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: Mon, 8 May 2023 01:40:35 +0200 [thread overview]
Message-ID: <02349503-4542-cbfd-2a2f-379fe8284cca@denx.de> (raw)
In-Reply-To: <TYCPR01MB847111D756F520761D720716C26A9@TYCPR01MB8471.jpnprd01.prod.outlook.com>
On 4/27/23 12:50, DLG Adam Ward wrote:
> On 18 April 2023 21:00, Christoph Niedermaier wrote:
>> In V3 of this patch the kernel test robot found an issue. A fix is important, because otherwise the normal path with IRQ could have problems. So I fixed it in V4. Any comments or is it OK how I fixed it?
>
> Hi Christoph,
>
> It looks fine now; sorry I didn't notice before.
I think a formal Reviewed-by / Acked-by would be nice.
But maybe Mark can pick this 3/3 patch now either way ?
next prev parent reply other threads:[~2023-05-07 23:40 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 [this message]
2023-05-09 8:59 ` DLG Adam Ward
2023-05-09 9:20 ` Marek Vasut
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=02349503-4542-cbfd-2a2f-379fe8284cca@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®