From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] Second set of IIO new device support, features and cleanups for the 5.3 cycle.
Date: Mon, 1 Jul 2019 10:59:58 +0200 [thread overview]
Message-ID: <20190701085958.GA11465@kroah.com> (raw)
In-Reply-To: <20190627204945.104a3af2@archlinux>
On Thu, Jun 27, 2019 at 08:49:45PM +0100, Jonathan Cameron wrote:
> The following changes since commit 1f48d056287d58f425c4f36705764f2ba802feba:
>
> MAINTAINERS: Add entry for anybuss drivers (2019-05-24 21:20:43 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.3b
Pulled and pushed out. NOte, there was one tiny merge issue that you
might want to check that I got correct.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-01 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 19:49 [PULL] Second set of IIO new device support, features and cleanups for the 5.3 cycle Jonathan Cameron
2019-07-01 8:59 ` Greg KH [this message]
2019-07-01 10:15 ` 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=20190701085958.GA11465@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