From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Stewart Smith <stewart@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, neelegup@linux.vnet.ibm.com,
stable@vger.kernel.org
Subject: Re: rtc-opal: Fix handling of firmware error codes, prevent busy loops
Date: Tue, 6 Feb 2018 13:42:12 +0100 [thread overview]
Message-ID: <20180206124212.GQ3404@piout.net> (raw)
In-Reply-To: <87bmh24rq0.fsf@concordia.ellerman.id.au>
On 06/02/2018 at 16:22:47 +1100, Michael Ellerman wrote:
> > Just a note to let you know that this patch should have gone through my
> > tree but it was not sent to linux-rtc or me.
>
> Sorry, I saw it had been languishing for a long time and assumed you'd
> missed it.
>
> Happy to revert/rework it if you're not happy with it.
>
No, that's fine. It's just that the commit title stands out when using
git log --oneline and that triggered my OCD ;)
> > I guess what happened is that Michael cleaned up the Linux PPC patchwork
> > queue.
>
> Yeah I did.
>
> In future I'll ping you if there's something that seems to have fallen
> through the cracks.
>
Great thanks!
--
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-06 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 1:50 [PATCH] rtc-opal: Fix handling of firmware error codes, prevent busy loops Stewart Smith
2016-08-03 7:12 ` Michael Ellerman
2018-01-29 4:13 ` Michael Ellerman
2018-02-06 2:26 ` Alexandre Belloni
2018-02-06 5:22 ` Michael Ellerman
2018-02-06 12:42 ` Alexandre Belloni [this message]
2018-02-06 14:06 ` Michael Ellerman
2018-02-06 7:57 ` Stewart Smith
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=20180206124212.GQ3404@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=neelegup@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=stewart@linux.vnet.ibm.com \
/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).