All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/5] IIO: Move the core out of staging.
Date: Wed, 25 Apr 2012 11:13:19 -0700	[thread overview]
Message-ID: <20120425181319.GA22984@kroah.com> (raw)
In-Reply-To: <1335365700-1138-1-git-send-email-jic23@kernel.org>

On Wed, Apr 25, 2012 at 03:54:55PM +0100, Jonathan Cameron wrote:
> Hi Greg,
> 
> Here is the promised patch series.
> 
> I stalled it for a few days over whether we should switch some of the
> Kconfig selects to depends.  Lars-Peter talked me out of it arguing
> it made little sense to users.  There are some cleanups to be made
> there but they can occur at a later date.
> 
> Clearly there are lots more docs to move, but some of those need going
> over with a fine toothed comb as they have rotted somewhat.  We'll
> work on that in the near future.

Very nicely done, I've applied this to the staging-next tree.

Congrats, now the real work begins :)

greg k-h

      parent reply	other threads:[~2012-04-25 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 14:54 [PATCH 0/5] IIO: Move the core out of staging Jonathan Cameron
2012-04-25 14:54 ` [PATCH 1/5] staging:iio:documentation pull a few sysfs entries out of main docs Jonathan Cameron
2012-04-25 14:54 ` [PATCH 2/5] staging:iio:Documentation Trivial typo fixes Jonathan Cameron
2012-04-25 14:54 ` [PATCH 3/5] IIO: Move core headers to include/linux/iio Jonathan Cameron
2012-04-25 14:54 ` [PATCH 4/5] IIO: Move the core files to drivers/iio Jonathan Cameron
2012-04-25 14:55 ` [PATCH 5/5] IIO: Move the core abi documentation from staging Jonathan Cameron
2012-04-25 18:13 ` Greg KH [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=20120425181319.GA22984@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.