From: Mark Brown <broonie@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: ChiYuan Huang <u0084500@gmail.com>,
djrscally@gmail.com, hdegoede@redhat.com, markgross@kernel.org,
lgirdwood@gmail.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, yangyingliang@huawei.com,
gene_chen@richtek.com, chiaen_wu@richtek.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
ChiYuan Huang <cy_huang@richtek.com>
Subject: Re: [PATCH v2] regulator: core: Use different devices for resource allocation and DT lookup
Date: Tue, 13 Dec 2022 16:32:21 +0000 [thread overview]
Message-ID: <Y5ipFd8BfU361QzN@sirena.org.uk> (raw)
In-Reply-To: <dc6c80f1-f34d-eaab-d561-32caa7fa140c@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Tue, Dec 13, 2022 at 03:29:00PM +0100, Marek Szyprowski wrote:
> On 13.12.2022 15:19, ChiYuan Huang wrote:
> > I don't have the board. Could you help to test this change to see
> > whether it's been fixed or not?
> The above change fixes the issue. Thanks! Feel free to add following
> tags to the final patch:
> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
Thanks for jumping on this so quickly! Marek, are these boards (or
similar ones) generally available? They seem great at showing up issues
so it'd be good if I could get them into my CI and spot problems earlier
(or something like kernelci.org would be about as good)?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-13 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 7:22 cy_huang
2022-12-08 14:09 ` Mark Brown
[not found] ` <CGME20221213113259eucas1p1c224898772bc5e59de90c1aa65a34de0@eucas1p1.samsung.com>
2022-12-13 11:32 ` Marek Szyprowski
2022-12-13 14:19 ` ChiYuan Huang
2022-12-13 14:29 ` Marek Szyprowski
2022-12-13 16:32 ` Mark Brown [this message]
2022-12-13 22:23 ` Marek Szyprowski
2022-12-14 13:32 ` Mark Brown
2022-12-14 0:35 ` ChiYuan Huang
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=Y5ipFd8BfU361QzN@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=djrscally@gmail.com \
--cc=gene_chen@richtek.com \
--cc=hdegoede@redhat.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=m.szyprowski@samsung.com \
--cc=markgross@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=u0084500@gmail.com \
--cc=yangyingliang@huawei.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®