[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170721225815.i6467grjen32x4kq@gmail.com>
Date: Sat, 22 Jul 2017 00:58:15 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Dan Williams <dan.j.williams@...el.com>
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?
* 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.
Thanks,
Ingo
Powered by blists - more mailing lists