From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Linux IIO List <linux-iio@vger.kernel.org>
Subject: Re: [PULL] IIO new drivers, features and cleanups for 3.17 - set 1
Date: Wed, 18 Jun 2014 20:04:22 -0700 [thread overview]
Message-ID: <20140619030422.GA26259@kroah.com> (raw)
In-Reply-To: <53A1D5D8.7060107@kernel.org>
On Wed, Jun 18, 2014 at 07:09:28PM +0100, Jonathan Cameron wrote:
> The following changes since commit 34683a5c6e0ffaa61528ff71c283efe3063cc53f:
>
> fix format string missmatch in staging/iio/Documentation/iio_utils.h (2014-05-25 12:09:37 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-3.17a
Pulled and pushed out, thanks.
greg k-h
prev parent reply other threads:[~2014-06-19 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 18:09 [PULL] IIO new drivers, features and cleanups for 3.17 - set 1 Jonathan Cameron
2014-06-19 3:04 ` Greg Kroah-Hartman [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=20140619030422.GA26259@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).