From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
Cc: Jonathan Cameron <jic23@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PULL] 5th set of IIO fixes for the 4.11 cycle.
Date: Tue, 18 Apr 2017 19:40:14 +0200 [thread overview]
Message-ID: <20170418174014.GC8087@kroah.com> (raw)
In-Reply-To: <0345D842-DDD5-43ED-B6B0-22FB5C627DDF@jic23.retrosnub.co.uk>
On Tue, Apr 18, 2017 at 05:18:30PM +0100, Jonathan Cameron wrote:
>
>
> On 18 April 2017 16:13:11 BST, Greg KH <gregkh@linuxfoundation.org> wrote:
> >On Fri, Apr 14, 2017 at 04:59:48PM +0100, Jonathan Cameron wrote:
> >> The following changes since commit
> >a6d361404d81a03107a3475876afc22e1b84d5de:
> >>
> >> Merge tag 'iio-fixes-for-4.11d' of
> >git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into
> >staging-linus (2017-04-03 15:28:14 +0200)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
> >tags/iio-fixes-for-4.11e
> >
> >Ugh, it's too late for 4.11, can I pull this into the -next branch and
> >just take it that way?
> >
> >Or do you want to redo this, with cc: stable markings to get into
> >4.11.1?
> >
> Might take me a little while to get to it, so pull into next branch and I'll send requests for stable
> once it hits mainline in the merge window.
Ok, now pulled in and pushed out in the staging-next branch.
thanks,
greg k-h
prev parent reply other threads:[~2017-04-18 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 15:59 [PULL] 5th set of IIO fixes for the 4.11 cycle Jonathan Cameron
2017-04-18 15:13 ` Greg KH
2017-04-18 16:18 ` Jonathan Cameron
2017-04-18 17:40 ` 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=20170418174014.GC8087@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jic23@jic23.retrosnub.co.uk \
--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.