From: Mahesh Khanwalkar <maheshkhanwalkar@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: sudeep.dutt@intel.com, ashutosh.dixit@intel.com,
tglx@linutronix.de, clemens@ladisch.de, wim@iguana.be,
linux@roeck-us.net, gregkh@linuxfoundation.org,
dasaratharaman.chandramouli@intel.com, timur@codeaurora.org,
arnd@arndb.de, nab@linux-iscsi.org, hans.verkuil@cisco.com,
mchehab@osg.samsung.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v4] Documentation: Move samples from doc to samples/
Date: Tue, 19 Jul 2016 18:53:27 -0400 [thread overview]
Message-ID: <20160719225327.GA3779@gmail.com> (raw)
In-Reply-To: <20160719163525.05af24af@lwn.net>
On Tue, Jul 19, 2016 at 04:35:25PM -0600, Jonathan Corbet wrote:
> So, while I'm generally in favor of moving this code over to samples/,
> I'm a bit nervous about a single, do-it-all patch. I'd rather see each
> subsystem's stuff moved separately, with (1) review from the appropriate
> maintainer, and (2) some sense that somebody has looked at this code and
> ensured that it still makes sense to keep around.
I agree. I'll break up the patch into smaller, independent pieces based
on the subsystem and email the appropriate maintainers. There were a few
other stuff referenced in Documentation/Makefile that may be samples
(I'll have to look again) that I didn't add to the patch, as it was
getting a quite large already.
Thanks,
Mahesh Khanwalkar
prev parent reply other threads:[~2016-07-19 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1468870350.1900.18.camel () perches ! com>
2016-07-18 19:55 ` [PATCH v4] Documentation: Move samples from doc to samples/ Mahesh Khanwalkar
2016-07-19 22:35 ` Jonathan Corbet
2016-07-19 22:46 ` Randy Dunlap
2016-07-19 22:53 ` Mahesh Khanwalkar [this message]
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=20160719225327.GA3779@gmail.com \
--to=maheshkhanwalkar@gmail.com \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=clemens@ladisch.de \
--cc=corbet@lwn.net \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--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=mchehab@osg.samsung.com \
--cc=nab@linux-iscsi.org \
--cc=sudeep.dutt@intel.com \
--cc=tglx@linutronix.de \
--cc=timur@codeaurora.org \
--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).