Re: Moving ndctl development into the kernel tree?

On 07/22/2017 02:49 PM, Dan Williams wrote: On Fri, Jul 21, 2017 at 7:52 PM, Dan Williams wrote: [ adding Chris ] On Fri, Jul 21, 2017 at 4:44 PM, Dan Williams wrote: On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar wrote:

Re: Moving ndctl development into the kernel tree?

On 07/22/2017 02:49 PM, Dan Williams wrote: On Fri, Jul 21, 2017 at 7:52 PM, Dan Williams wrote: [ adding Chris ] On Fri, Jul 21, 2017 at 4:44 PM, Dan Williams wrote: On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar wrote: * Dan Williams wrote: [...] * Like perf, ndctl borrows the

Re: Moving ndctl development into the kernel tree?

On Fri, Jul 21, 2017 at 7:52 PM, Dan Williams wrote: > [ adding Chris ] > > On Fri, Jul 21, 2017 at 4:44 PM, Dan Williams > wrote: >> On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar wrote: >>> >>> * Dan Williams

Re: Moving ndctl development into the kernel tree?

On Fri, Jul 21, 2017 at 7:52 PM, Dan Williams wrote: > [ adding Chris ] > > On Fri, Jul 21, 2017 at 4:44 PM, Dan Williams > wrote: >> On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar wrote: >>> >>> * Dan Williams wrote: >>> [...] * Like perf, ndctl borrows the sub-command

Re: Moving ndctl development into the kernel tree?

[ adding Chris ] On Fri, Jul 21, 2017 at 4:44 PM, Dan Williams wrote: > On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar wrote: >> >> * Dan Williams wrote: >> >>> [...] >>> >>> * Like perf, ndctl borrows the sub-command

Re: Moving ndctl development into the kernel tree?

[ adding Chris ] On Fri, Jul 21, 2017 at 4:44 PM, Dan Williams wrote: > On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar wrote: >> >> * Dan Williams wrote: >> >>> [...] >>> >>> * Like perf, ndctl borrows the sub-command architecture and option >>> parsing from git. So, this code could be

Re: Moving ndctl development into the kernel tree?

On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar wrote: > > * Dan Williams wrote: > >> [...] >> >> * Like perf, ndctl borrows the sub-command architecture and option >> parsing from git. So, this code could be refactored into something >> shared / generic,

Re: Moving ndctl development into the kernel tree?

On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar wrote: > > * Dan Williams wrote: > >> [...] >> >> * Like perf, ndctl borrows the sub-command architecture and option >> parsing from git. So, this code could be refactored into something >> shared / generic, i.e. the bits in tools/perf/util/. > > Just

Re: Moving ndctl development into the kernel tree?

* Dan Williams wrote: > [...] > > * Like perf, ndctl borrows the sub-command architecture and option > parsing from git. So, this code could be refactored into something > shared / generic, i.e. the bits in tools/perf/util/. Just as a side note, stacktool

Re: Moving ndctl development into the kernel tree?

* Dan Williams wrote: > [...] > > * Like perf, ndctl borrows the sub-command architecture and option > parsing from git. So, this code could be refactored into something > shared / generic, i.e. the bits in tools/perf/util/. Just as a side note, stacktool (tools/stacktool/) is using the Git

Moving ndctl development into the kernel tree?

Hi Linus, Would you be open to the ndctl [1] project moving its development into the kernel tree? The main reasons why I ask are: * Unit test development can touch both the kernel-side emulated nvdimm infrastructure in tools/testing/nvdimm/ and the corresponding tests in tools/ndctl/test/ in the

Moving ndctl development into the kernel tree?

Hi Linus, Would you be open to the ndctl [1] project moving its development into the kernel tree? The main reasons why I ask are: * Unit test development can touch both the kernel-side emulated nvdimm infrastructure in tools/testing/nvdimm/ and the corresponding tests in tools/ndctl/test/ in the