From: Marek Vasut <marex@denx.de>
To: DLG Adam Ward <DLG-Adam.Ward.opensource@dm.renesas.com>,
Christoph Niedermaier <cniedermaier@dh-electronics.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Support Opensource <support.opensource@diasemi.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
kernel <kernel@dh-electronics.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 3/3] regulator: da9062: Make the use of IRQ optional
Date: Tue, 9 May 2023 11:20:43 +0200 [thread overview]
Message-ID: <e7e4f933-5098-5fea-7a1d-254609c93cbd@denx.de> (raw)
In-Reply-To: <OS3PR01MB8460C4A6047EE4590D4F791FC2769@OS3PR01MB8460.jpnprd01.prod.outlook.com>
On 5/9/23 10:59, DLG Adam Ward wrote:
> On 08 May 2023 00:41, Marek Vasut wrote:
>
>>> It looks fine now; sorry I didn't notice before.
>>
>> I think a formal Reviewed-by / Acked-by would be nice.
>
> It's already there in the patch - obliquely referred to by "before", the apology because I'd missed that which the robot picked up on after I'd looked at it.
Ahh, in that case, sorry for the noise and thanks for the RB .
And for all its worth, patch is also:
Reviewed-by: Marek Vasut <marex@denx.de>
next prev parent reply other threads:[~2023-05-09 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 9:22 [PATCH V4 1/3] mfd: da9062: Use MFD_CELL_OF macro Christoph Niedermaier
2023-03-09 9:22 ` [PATCH V4 2/3] mfd: da9062: Remove IRQ requirement Christoph Niedermaier
2023-03-16 14:00 ` Lee Jones
2023-03-09 9:22 ` [PATCH V4 3/3] regulator: da9062: Make the use of IRQ optional Christoph Niedermaier
2023-04-18 20:00 ` Christoph Niedermaier
2023-04-27 10:50 ` DLG Adam Ward
2023-05-07 23:40 ` Marek Vasut
2023-05-09 8:59 ` DLG Adam Ward
2023-05-09 9:20 ` Marek Vasut [this message]
2023-07-12 13:19 ` Christoph Niedermaier
2023-07-13 9:18 ` Christoph Niedermaier
2023-03-16 13:59 ` [PATCH V4 1/3] mfd: da9062: Use MFD_CELL_OF macro Lee Jones
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=e7e4f933-5098-5fea-7a1d-254609c93cbd@denx.de \
--to=marex@denx.de \
--cc=DLG-Adam.Ward.opensource@dm.renesas.com \
--cc=broonie@kernel.org \
--cc=cniedermaier@dh-electronics.com \
--cc=kernel@dh-electronics.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=support.opensource@diasemi.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®