From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Liam Girdwood <lgirdwood@gmail.com>, Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] regulator: bd96801: Add ERRB IRQ
Date: Thu, 14 Nov 2024 14:04:09 +0200 [thread overview]
Message-ID: <80071b1c-c8e1-4273-8b10-3630af8d88e8@gmail.com> (raw)
In-Reply-To: <ZzXjvHvOlP6VCzcI@finisterre.sirena.org.uk>
On 14/11/2024 13:49, Mark Brown wrote:
> On Thu, Nov 14, 2024 at 09:19:59AM +0200, Matti Vaittinen wrote:
>
>> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
>> Reviewed-by: Mark Brown <broonie@kernel.org>
>> ---
>>
>> This patch was part of the:
>> https://lore.kernel.org/all/cover.1727931468.git.mazziesaccount@gmail.com/
>> The MFD part was applied by Lee, but I didn't see the regulator part in
>> MFD or regulator repository. Perhaps it fell through the cracks? I know
>> we're late in the cycle but I re-spin this now before I forgot... We do
>> always have the next cycle, right? :)
>
> If this is part of a MFD series I'd have expected it to go in with
> that...
AFAIR, Lee asked if the patches could be taken in separately. I replied
"yes" - with a very small corner case of someone having the ERRB in
device-tree already (which could've been a problem if regulator part
went in and MFD didn't). After this Lee picked only the subset. I
suppose this evaded your eye :) I know I should've resent this back
then, but I just forgot to check if you picked this.
I don't see having the MFD part in without the regulators a problem
(other than missing the ERRB functionality). So, perhaps Mark can pick
this after v6.13-rc1 is out?
Yours,
-- Matti
next prev parent reply other threads:[~2024-11-14 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 7:19 Matti Vaittinen
2024-11-14 11:49 ` Mark Brown
2024-11-14 12:04 ` Matti Vaittinen [this message]
2024-12-02 13:16 ` Mark Brown
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=80071b1c-c8e1-4273-8b10-3630af8d88e8@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=broonie@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.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
all inboxes | Powered by JetHome®