Messages in this thread | | | Date | Fri, 25 Oct 2013 11:00:01 +0800 | Subject | Re: ktap inclusion in drivers/staging/? | From | Jovi Zhangwei <> |
| |
On Fri, Oct 25, 2013 at 3:46 AM, Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote: > Em Thu, Oct 24, 2013 at 08:11:36PM +0800, Jovi Zhangwei escreveu: >> I admit there have many places need to cleanup in ktap code, and there >> also have a long todo list, I will finish it before start review process. >> >> Again, really sorry for this, please forgive me this mistake. > > Just go eroding it, try to figure out things that could be useful on its > own, find the right place in the tree, send a flow of small self > contained patches that comes with tooling that uses whatever new kernel > feature that is added. > > I think that even if you just add a 'perf test' entry that shows how the > new feature should be used by tooling, exercising it and checking its > results, so that every time people try 'perf test' it gets re verified, > that would be ok when no other tools/ living source code exercises it. >
Nice, I will take some time to look at it.
Thank you.
Jovi
| |