Linux IIO development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL V2] First round of new device support, cleanups and fixes for IIO in the 5.2 cycle.
Date: Thu, 4 Apr 2019 22:33:48 +0200	[thread overview]
Message-ID: <20190404203348.GA13409@kroah.com> (raw)
In-Reply-To: <20190404205720.66804920@archlinux>

On Thu, Apr 04, 2019 at 08:57:20PM +0100, Jonathan Cameron wrote:
> The following changes since commit b397f82585c3101dcf92642dd359891e66d00c55:
> 
>   Merge 5.1-rc3 into staging-next (2019-04-01 07:49:24 +0200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.2a-2

Looks good, now pulled and pushed out.

greg k-h

      reply	other threads:[~2019-04-04 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 19:57 [PULL V2] First round of new device support, cleanups and fixes for IIO in the 5.2 cycle Jonathan Cameron
2019-04-04 20:33 ` 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=20190404203348.GA13409@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