[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160719225327.GA3779@gmail.com>
Date: Tue, 19 Jul 2016 18:53:27 -0400
From: Mahesh Khanwalkar <maheshkhanwalkar@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: sudeep.dutt@...el.com, ashutosh.dixit@...el.com,
tglx@...utronix.de, clemens@...isch.de, wim@...ana.be,
linux@...ck-us.net, gregkh@...uxfoundation.org,
dasaratharaman.chandramouli@...el.com, timur@...eaurora.org,
arnd@...db.de, nab@...ux-iscsi.org, hans.verkuil@...co.com,
mchehab@....samsung.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pcmcia@...ts.infradead.org,
linux-watchdog@...r.kernel.org
Subject: Re: [PATCH v4] Documentation: Move samples from doc to samples/
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
Powered by blists - more mailing lists