[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4iNuUpVE=n7sY+OD3eRxeQeskNuU6QC2j=xxFB3bpWiSA@mail.gmail.com>
Date: Fri, 21 Jul 2017 16:44:51 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
Johannes Thumshirn <jthumshirn@...e.de>,
jmoyer <jmoyer@...hat.com>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
"Oliver O'Halloran" <oohall@...il.com>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: Moving ndctl development into the kernel tree?
On Fri, Jul 21, 2017 at 3:58 PM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * Dan Williams <dan.j.williams@...el.com> 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 sub-command and
> options parsing code as well, and it's already sharing it with perf, via the
> tools/lib/subcmd/ library.
>
> ndctl could use that as well.
Ah, nice, that refactoring happened about a year after ndctl was born.
Which brings up the next question about what to do with the git
history, but I'd want to know if ndctl is even welcome upstream before
digging any deeper.
Powered by blists - more mailing lists