public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: corbet@lwn.net, davem@davemloft.net, nicolas.dichtel@6wind.com,
	elfring@users.sourceforge.net, geert@linux-m68k.org,
	akpm@linux-foundation.org, kvalo@codeaurora.org,
	mchehab@kernel.org, linux@roeck-us.net,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pcmcia@lists.infradead.org
Subject: Re: [PATCH v2 3/3] tools: move pcmcia crc32hash tool from Documentation
Date: Thu, 22 Sep 2016 07:14:59 +0200	[thread overview]
Message-ID: <20160922051459.GA12883@kroah.com> (raw)
In-Reply-To: <6125e1c8c96924d869fb847b676f544c4d03cb8a.1474500009.git.shuahkh@osg.samsung.com>

On Wed, Sep 21, 2016 at 06:51:13PM -0600, Shuah Khan wrote:
> Move pcmcia crc32hash tool from Documentation to tools/pcmcia and
> remove it from Documentation Makefile. Update location information
> for this tool. Create a new Makefile to build pcmcia. It can be built
> from top level directory or from pcmcia directory:
> 
> Run make -C tools/pcmcia or cd tools/pcmcia; make
> 
> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> ---
>  Documentation/Makefile               |  3 +--
>  Documentation/pcmcia/.gitignore      |  1 -
>  Documentation/pcmcia/Makefile        |  7 -------
>  Documentation/pcmcia/crc32hash.c     | 32 --------------------------------
>  Documentation/pcmcia/devicetable.txt |  4 ++--
>  MAINTAINERS                          |  1 +
>  tools/pcmcia/.gitignore              |  1 +
>  tools/pcmcia/Makefile                |  9 +++++++++
>  tools/pcmcia/crc32hash.c             | 32 ++++++++++++++++++++++++++++++++
>  9 files changed, 46 insertions(+), 44 deletions(-)
>  delete mode 100644 Documentation/pcmcia/.gitignore
>  delete mode 100644 Documentation/pcmcia/Makefile
>  delete mode 100644 Documentation/pcmcia/crc32hash.c
>  create mode 100644 tools/pcmcia/.gitignore
>  create mode 100644 tools/pcmcia/Makefile
>  create mode 100644 tools/pcmcia/crc32hash.c


Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  reply	other threads:[~2016-09-22  5:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  0:51 [PATCH v2 0/3] Move runnable tools from Documentation to tools Shuah Khan
2016-09-22  0:51 ` [PATCH v2 1/3] tools: move accounting tool from Documentation Shuah Khan
2016-09-22  0:51 ` [PATCH v2 2/3] tools: move laptops dslm " Shuah Khan
2016-09-22  0:51 ` [PATCH v2 3/3] tools: move pcmcia crc32hash " Shuah Khan
2016-09-22  5:14   ` Greg KH [this message]
2016-09-22  7:31   ` Dominik Brodowski
2016-09-22 14:57 ` [PATCH v2 0/3] Move runnable tools from Documentation to tools Jonathan Corbet
2016-09-23 13:59   ` Shuah Khan

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=20160922051459.GA12883@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=elfring@users.sourceforge.net \
    --cc=geert@linux-m68k.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --cc=mchehab@kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=shuahkh@osg.samsung.com \
    /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