From: Joe Perches <joe@perches.com>
To: Mahesh Khanwalkar <maheshkhanwalkar@gmail.com>,
corbet@lwn.net, 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
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pcmcia@lists.infradead.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3] Documentation: Move samples from doc to samples/
Date: Mon, 18 Jul 2016 12:32:30 -0700 [thread overview]
Message-ID: <1468870350.1900.18.camel@perches.com> (raw)
In-Reply-To: <1468870066-11792-1-git-send-email-maheshkhanwalkar@gmail.com>
On Mon, 2016-07-18 at 15:27 -0400, Mahesh Khanwalkar 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.
The MAINTAINERS file should also have file patterns updated.
prev parent reply other threads:[~2016-07-18 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <578D2264.6060205 () codeaurora ! org>
2016-07-18 19:27 ` [PATCH v3] Documentation: Move samples from doc to samples/ Mahesh Khanwalkar
2016-07-18 19:32 ` Joe Perches [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=1468870350.1900.18.camel@perches.com \
--to=joe@perches.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=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