From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] 2nd set of IIO fixes for the 5.13 cycle.
Date: Sat, 22 May 2021 08:35:47 +0100 [thread overview]
Message-ID: <20210522083547.2570d4b6@jic23-huawei> (raw)
In-Reply-To: <YKf5S+avRha12kAW@kroah.com>
On Fri, 21 May 2021 20:17:47 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
> On Fri, May 21, 2021 at 08:12:48PM +0200, Greg KH wrote:
> > On Fri, May 21, 2021 at 06:15:09PM +0100, Jonathan Cameron wrote:
> > > The following changes since commit ba9c25d94dea1a57492a606a1f5dde70d2432583:
> > >
> > > Merge tag 'iio-fixes-5.13a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus (2021-05-11 15:17:55 +0200)
> > >
> > > are available in the Git repository at:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-5.13b
> >
> > Pulled and pushed out, thanks.
>
> Oops, nope, didn't work:
>
> Commit 488abb0f5c83 ("iio: gyro: fxas21002c: balance runtime power in error path")
> committer Signed-off-by missing
> author email: rui.silva@linaro.org
> committer email: Jonathan.Cameron@huawei.com
> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>
>
> I've rolled it back in my local tree and never pushed it out to the
> public.
>
> Can you fix this up? linux-next didn't catch this already?
>
I'll check, but didn't see anything. Perhaps an email filtering issue my end.
Anyhow, thanks for catching and will send fixed up version in a few mins.
Jonathan
> thanks,
>
> greg k-h
prev parent reply other threads:[~2021-05-22 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 17:15 [PULL] 2nd set of IIO fixes for the 5.13 cycle Jonathan Cameron
2021-05-21 18:12 ` Greg KH
2021-05-21 18:17 ` Greg KH
2021-05-22 7:35 ` Jonathan Cameron [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=20210522083547.2570d4b6@jic23-huawei \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.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