From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] 3rd set of new IIO device support, features, cleanups and fixes for the 4.19 cycle.
Date: Wed, 1 Aug 2018 20:30:55 +0200 [thread overview]
Message-ID: <20180801183055.GA1982@kroah.com> (raw)
In-Reply-To: <20180801192232.3eb71a44@archlinux>
On Wed, Aug 01, 2018 at 07:22:32PM +0100, Jonathan Cameron wrote:
> This is a somewhat sneaky late pull request given Linus has announced
> a likely 1 week delay. If it is too late I'll resend after the merge
> window. I merged in the fixes branch as those are primarily around
> things queued for the merge window.
>
> Particulary good to see the output of our Himanshu Jha, a GSOC student
> who developed the bme680 driver.
I don't see a url/tag to pull from here :(
next prev parent reply other threads:[~2018-08-01 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 18:22 [PULL] 3rd set of new IIO device support, features, cleanups and fixes for the 4.19 cycle Jonathan Cameron
2018-08-01 18:30 ` Greg KH [this message]
2018-08-01 18:54 ` Jonathan Cameron
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=20180801183055.GA1982@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).