From: Michael Ellerman <mpe@ellerman•id.au>
To: Alexandre Belloni <alexandre.belloni@bootlin•com>,
Nicholas Piggin <npiggin@gmail•com>
Cc: linux-rtc@vger•kernel.org, linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH 2/3] powerpc/powernv: Fix OPAL RTC driver OPAL_BUSY loops
Date: Wed, 25 Apr 2018 13:28:27 +1000 [thread overview]
Message-ID: <87d0yo55ic.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180424183918.GF19011@piout.net>
Alexandre Belloni <alexandre.belloni@bootlin•com> writes:
> On 10/04/2018 23:01:36+1000, Nicholas Piggin wrote:
>> On Tue, 10 Apr 2018 14:07:28 +0200
>> Alexandre Belloni <alexandre.belloni@bootlin•com> wrote:
>> > > Fixes ("powerpc/powernv: Add RTC and NVRAM support plus RTAS fallbacks"
>> > > Cc: Benjamin Herrenschmidt <benh@kernel•crashing.org>
>> > > Cc: linux-rtc@vger•kernel.org
>> > > Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
>> > > ---
>> > > arch/powerpc/platforms/powernv/opal-rtc.c | 8 +++--
>> > > drivers/rtc/rtc-opal.c | 37 ++++++++++++++---------
>> >
>> > From what I understand, the changes in those files are fairly
>> > independent, they should probably be separated to ease merging.
>>
>> I'm happy to do that. It's using the same firmware call, so I thought
>> a single patch would be fine. But I guess the boot call can be
>> dropped from this patch because it does not not solve the problem
>> described in the changelog.
>>
>> Would you be happy for the driver change to be merged via the powerpc
>> tree? The code being fixed here came from the same original patch as
>> a similar issue being fixed in the OPAL NVRAM driver so it might be
>> easier that way.
>
> Ok then, just add my
>
> Acked-by: Alexandre Belloni <alexandre.belloni@bootlin•com>
>
> and let it go through the powerpc tree.
Thanks.
It's still mostly an rtc patch by lines changed, so I changed the
subject to:
rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops
cheers
next prev parent reply other threads:[~2018-04-25 3:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 11:49 [PATCH 0/3] Fix RTC and NVRAM OPAL_BUSY loops Nicholas Piggin
2018-04-10 11:49 ` [PATCH 1/3] powerpc/powernv: define a standard delay for OPAL_BUSY type retry loops Nicholas Piggin
2018-04-11 14:49 ` [1/3] " Michael Ellerman
2018-04-10 11:49 ` [PATCH 2/3] powerpc/powernv: Fix OPAL RTC driver OPAL_BUSY loops Nicholas Piggin
2018-04-10 12:07 ` Alexandre Belloni
2018-04-10 13:01 ` Nicholas Piggin
2018-04-24 18:39 ` Alexandre Belloni
2018-04-25 3:28 ` Michael Ellerman [this message]
2018-04-25 9:41 ` Alexandre Belloni
2018-04-26 10:22 ` [2/3] " Michael Ellerman
2018-04-10 11:49 ` [PATCH 3/3] powerpc/powernv: Fix OPAL NVRAM " Nicholas Piggin
2018-04-11 14:49 ` [3/3] " Michael Ellerman
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=87d0yo55ic.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=linux-rtc@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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