public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mahesh Khanwalkar <maheshkhanwalkar@gmail.com>
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 16:35:25 -0600	[thread overview]
Message-ID: <20160719163525.05af24af@lwn.net> (raw)
In-Reply-To: <1468871700-12889-1-git-send-email-maheshkhanwalkar@gmail.com>

On Mon, 18 Jul 2016 15:55:00 -0400
Mahesh Khanwalkar <maheshkhanwalkar@gmail.com> wrote:

> Moved sample code found in Documentation/ to samples/ but kept actual
> documentation where it is, while updating any in-text references to the
> moved code. Updated the Documentation/Makefile and samples/Makefile to
> reflect the change. Built with CONFIG_SAMPLES=y in .config with no
> build errors. The directories added within samples/ still follow the
> same structure that they did in Documentation. Directories in
> Documentation/ that contained code still exist, only the code within
> them has been moved out accordingly.

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.

For example, pcmcia/crc32hash.c predates the git era and has only seen
trivial changes in living memory.  I have this vague sense that the
number of new PCMCIA cards needing addition is pretty small these days.
Rather than move it to samples/ (what is it a sample of?), we might want
to consider just getting rid of it.

Thanks,

jon

  reply	other threads:[~2016-07-19 22:35 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 [this message]
2016-07-19 22:46     ` Randy Dunlap
2016-07-19 22:53     ` Mahesh Khanwalkar

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=20160719163525.05af24af@lwn.net \
    --to=corbet@lwn.net \
    --cc=arnd@arndb.de \
    --cc=ashutosh.dixit@intel.com \
    --cc=clemens@ladisch.de \
    --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=maheshkhanwalkar@gmail.com \
    --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