From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PULL] IIO fixes
Date: Mon, 9 Jul 2012 13:38:53 -0700 [thread overview]
Message-ID: <20120709203853.GA29046@kroah.com> (raw)
In-Reply-To: <4FF9DFB7.70903@kernel.org>
On Sun, Jul 08, 2012 at 08:29:59PM +0100, Jonathan Cameron wrote:
> Hi Greg,
>
> To get a clean start on doing this without merges this is on top of
> your staging/staging-next tree of a few days back.
>
> I 'think' the signed tag should be correct.
>
> All comments welcome.
>
> The following changes since commit 0932966b1ca03217c6e0c18375867b1a99ee5af0:
>
> staging: ccg: print MAC addresses via %pM (2012-07-06 16:24:00 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
> tags/fixes-togreg_8_7_2012
What's with the line-wrap?
And the numbers after "togreg"? What's that for?
>
> for you to fetch changes up to 7b7627410e2c211f24787f61e6419e16d259aa13:
>
> iio: Fix inkern remove incorrect put of device (2012-07-08 20:02:31 +0100)
>
> ----------------------------------------------------------------
> Mixed bag of IIO fixes.
>
> Quite a few cases of interrupt handlers returning
> errors and a few more specific bits and bobs.
>
> Most of these only effect fairly obscure error
> paths. The IRQF_ONESHOT one may cause trouble
> given the requests will now be rejected.
>
> Jonathan
>
> 8_7_2012
The date perhaps? I've not seen that in a commit message before, I
doubt it's needed :)
Other than those minor things, looks good, I've pulled and pushed this
out.
thanks,
greg k-h
prev parent reply other threads:[~2012-07-09 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 19:29 [PULL] IIO fixes Jonathan Cameron
2012-07-09 20:38 ` 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=20120709203853.GA29046@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 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.