public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: davem@davemloft.net, nicolas.dichtel@6wind.com,
	elfring@users.sourceforge.net, geert@linux-m68k.org,
	akpm@linux-foundation.org, gregkh@linuxfoundation.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 0/3] Move runnable tools from Documentation to tools
Date: Thu, 22 Sep 2016 08:57:48 -0600	[thread overview]
Message-ID: <20160922085748.16894b15@lwn.net> (raw)
In-Reply-To: <cover.1474500008.git.shuahkh@osg.samsung.com>

On Wed, 21 Sep 2016 18:51:10 -0600
Shuah Khan <shuahkh@osg.samsung.com> wrote:

> Move runnable tools from Documentation to tools. I moved just the
> tools code, and left documentation files as is.
> 
> Based on the v1 series feedback, This v2 series moves accounting,
> laptops/dslm, and pcmcia to tools.
> 
> If v2 patches look good, and if I get an okay, I will try to get
> these into 4.9-rc1

Acked-by: Jonathan Corbet <corbet@lwn.net>

Though I still wonder if we really need to keep some of those tools...

jon

  parent reply	other threads:[~2016-09-22 14:57 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
2016-09-22  7:31   ` Dominik Brodowski
2016-09-22 14:57 ` Jonathan Corbet [this message]
2016-09-23 13:59   ` [PATCH v2 0/3] Move runnable tools from Documentation to tools 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=20160922085748.16894b15@lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=elfring@users.sourceforge.net \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.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