Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755000AbdGUW6U (ORCPT ); Fri, 21 Jul 2017 18:58:20 -0400 Received: from mail-wm0-f50.google.com ([74.125.82.50]:37999 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754806AbdGUW6T (ORCPT ); Fri, 21 Jul 2017 18:58:19 -0400 Date: Sat, 22 Jul 2017 00:58:15 +0200 From: Ingo Molnar To: Dan Williams Cc: "torvalds@linux-foundation.org" , Johannes Thumshirn , jmoyer , "linux-nvdimm@lists.01.org" , "linux-kernel@vger.kernel.org" , Ingo Molnar , Arnaldo Carvalho de Melo , "Oliver O'Halloran" , Arnaldo Carvalho de Melo , Jiri Olsa , Namhyung Kim , Peter Zijlstra Subject: Re: Moving ndctl development into the kernel tree? Message-ID: <20170721225815.i6467grjen32x4kq@gmail.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 492 Lines: 18 * 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 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