From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PULL] Second set of new IIO device support and cleanups for the 4.12 cycle
Date: Wed, 22 Mar 2017 12:00:32 +0100 [thread overview]
Message-ID: <20170322110032.GA2766@kroah.com> (raw)
In-Reply-To: <2efca4ba-3c59-6d57-6049-b0f4867b2d43@kernel.org>
On Tue, Mar 21, 2017 at 07:17:00PM +0000, Jonathan Cameron wrote:
> The following changes since commit 1d3da3fed1a211d11d33aff1fb2438a1fc27740e:
>
> atomisp: USE_KMEM_CACHE is always defined so remove the dead code (2017-03-08 13:40:00 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-4.12b
Pulled and pushed out, thanks!
greg k-h
prev parent reply other threads:[~2017-03-22 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 19:17 [PULL] Second set of new IIO device support and cleanups for the 4.12 cycle Jonathan Cameron
2017-03-22 11:00 ` 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=20170322110032.GA2766@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).