From: Alina Yu <alina_yu@richtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: ChiYuan Huang <cy_huang@richtek.com>, <lgirdwood@gmail.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <alina_yu@richtek.com>
Subject: Re: [PATCH v5 2/2] regulator: rtq2208: Add Richtek RTQ2208 SubPMIC driver
Date: Mon, 7 Aug 2023 14:34:31 +0800 [thread overview]
Message-ID: <20230807063431.GA31530@linuxcarl2.richtek.com> (raw)
In-Reply-To: <e31b8381-7148-4485-834a-02638e9a81d7@sirena.org.uk>
Hi
Mark,
On Thu, Aug 03, 2023 at 12:08:28PM +0100, Mark Brown wrote:
> On Thu, Aug 03, 2023 at 03:24:25PM +0800, ChiYuan Huang wrote:
> > On Wed, Jul 26, 2023 at 03:13:12PM +0800, Alina Yu wrote:
>
> > > Signed-off-by: Alina Yu <alina_yu@richtek.com>
> > > Reported-by: kernel test robot <lkp@intel.com>
> > This patch series is to add new drivers, not fix.
> > Why do you add the Reported-by tag?
>
> The LKP people have some boilerplate in their reports that tells people
> to add Reported-bys for things they find based on patches, it's a
> constant problem :(
Sorry, I misunerstood the meaning of Reported-by
I've removed that since v6.
Thanks, Alina
prev parent reply other threads:[~2023-08-07 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 7:13 [PATCH v5 0/2] Add Richtek RTQ2208 SubPMIC support Alina Yu
2023-07-26 7:13 ` [PATCH v5 1/2] regulator: dt-bindings: rtq2208: Add Richtek RTQ2208 SubPMIC Alina Yu
2023-07-26 9:53 ` Krzysztof Kozlowski
2023-08-03 6:36 ` ChiYuan Huang
2023-08-05 21:27 ` Krzysztof Kozlowski
2023-08-07 6:13 ` Alina Yu
2023-07-26 7:13 ` [PATCH v5 2/2] regulator: rtq2208: Add Richtek RTQ2208 SubPMIC driver Alina Yu
2023-08-03 7:24 ` ChiYuan Huang
2023-08-03 11:08 ` Mark Brown
2023-08-07 6:34 ` Alina Yu [this message]
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=20230807063431.GA31530@linuxcarl2.richtek.com \
--to=alina_yu@richtek.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).