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 IIO fixes for the 4.5 cycle - dependent on merge window patches.
Date: Mon, 1 Feb 2016 13:09:01 -0800 [thread overview]
Message-ID: <20160201210901.GC10149@kroah.com> (raw)
In-Reply-To: <56AFBE60.7030509@kernel.org>
On Mon, Feb 01, 2016 at 08:21:52PM +0000, Jonathan Cameron wrote:
> The following changes since commit 02c34ccc1d2d528d2de2897881b97933363432b5:
>
> Merge tag 'iio-for-4.5c' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next (2015-12-26 17:05:25 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-4.5b
Pulled and pushed out, thanks.
greg k-h
prev parent reply other threads:[~2016-02-01 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 20:21 [PULL] Second set of IIO fixes for the 4.5 cycle - dependent on merge window patches Jonathan Cameron
2016-02-01 21:09 ` 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=20160201210901.GC10149@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).