From: Jonathan Corbet <corbet@lwn.net>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: sudeep.dutt@intel.com, ashutosh.dixit@intel.com,
tomas.winkler@intel.com, tglx@linutronix.de, wim@iguana.be,
linux@roeck-us.net, elfring@users.sourceforge.net,
nicolas.dichtel@6wind.com, davem@davemloft.net,
gregkh@linuxfoundation.org,
dasaratharaman.chandramouli@intel.com,
maheshkhanwalkar@gmail.com, mikedanese@google.com,
ben@decadent.org.uk, ghackmann@google.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pcmcia@lists.infradead.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 1/8] samples: move accounting example code from Documentation
Date: Mon, 19 Sep 2016 10:02:20 -0600 [thread overview]
Message-ID: <20160919100220.3581d122@lwn.net> (raw)
In-Reply-To: <a73182df44d0827ed6338c082a8ea16d6d2bd0b8.1474073857.git.shuahkh@osg.samsung.com>
On Mon, 19 Sep 2016 08:47:32 -0600
Shuah Khan <shuahkh@osg.samsung.com> wrote:
> Move accounting examples to samples and remove it from Documentation
> Makefile. Create a new Makefile to build accounting. It can be built
> from top level directory or from accounting directory:
So I like the basic idea of these patches; it's the direction we've been
trying to push things for a little bit. I have a couple of specific
comments for this one that may well apply to the others as well.
1) Is samples the right destination for these utilities? Some of them
might well be better placed under tools/ instead. I'm not sure we've
ever formally stated the purpose of those two subtrees; I see samples/
as demonstrations of how to use something, while tools/ are utilities
you might actually want to use for some purpose. Something like
getdelays might well fall into the latter group. But maybe others
disagree?
2) Tools like getdelays are referenced in the documents that have been
left behind; see accounting/delay-accounting.txt, for example. Those
documents should be updated so that readers know where to find the
referenced programs, wherever they end up. Converting them to Sphinx
while you're at it is an extra-credit exercise :)
Thanks,
jon
next prev parent reply other threads:[~2016-09-19 16:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 14:47 [PATCH 0/8] Move runnable examples code from Documentation to samples Shuah Khan
2016-09-19 14:47 ` [PATCH 1/8] samples: move accounting example code from Documentation Shuah Khan
2016-09-19 16:02 ` Jonathan Corbet [this message]
2016-09-20 16:05 ` Shuah Khan
2016-09-19 14:47 ` [PATCH 2/8] samples: move auxdisplay " Shuah Khan
2016-09-19 16:05 ` Jonathan Corbet
2016-09-19 19:50 ` SF Markus Elfring
2016-09-20 16:09 ` [PATCH 2/8] " Shuah Khan
2016-09-19 14:47 ` [PATCH 3/8] samples: move laptops " Shuah Khan
2016-09-19 16:10 ` Jonathan Corbet
2016-09-20 16:11 ` Shuah Khan
2016-09-19 14:47 ` [PATCH 5/8] samples: move misc-devices/mei " Shuah Khan
2016-09-19 16:13 ` Jonathan Corbet
2016-09-20 6:17 ` Winkler, Tomas
2016-09-20 17:20 ` Shuah Khan
2016-09-19 14:47 ` [PATCH 6/8] samples: move pcmcia " Shuah Khan
2016-09-19 16:16 ` Jonathan Corbet
2016-09-19 14:47 ` [PATCH 7/8] samples: move timers " Shuah Khan
2016-09-19 16:18 ` Jonathan Corbet
2016-09-19 14:47 ` [PATCH 8/8] samples: move watchdog " Shuah Khan
2016-09-19 16:20 ` Jonathan Corbet
2016-09-19 15:42 ` [PATCH 0/8] Move runnable examples code from Documentation to samples Jani Nikula
[not found] ` <35cb90958701b063c5dd9874b08b5c5e970c0ce6.1474073857.git.shuahkh@osg.samsung.com>
2016-09-19 16:11 ` [PATCH 4/8] samples: move mic/mpssd example code from Documentation Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160919100220.3581d122@lwn.net \
--to=corbet@lwn.net \
--cc=ashutosh.dixit@intel.com \
--cc=ben@decadent.org.uk \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=davem@davemloft.net \
--cc=elfring@users.sourceforge.net \
--cc=ghackmann@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=maheshkhanwalkar@gmail.com \
--cc=mikedanese@google.com \
--cc=nicolas.dichtel@6wind.com \
--cc=shuahkh@osg.samsung.com \
--cc=sudeep.dutt@intel.com \
--cc=tglx@linutronix.de \
--cc=tomas.winkler@intel.com \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).