From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Support Opensource <support.opensource@diasemi.com>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
Liam Girdwood <lgirdwood@gmail.com>, Marek Vasut <marex@denx.de>,
kernel <kernel@dh-electronics.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH V5] regulator: da9062: Make the use of IRQ optional
Date: Fri, 14 Jul 2023 20:27:45 +0000 [thread overview]
Message-ID: <ef02362fdb5546e4962f1793659f2a54@dh-electronics.com> (raw)
In-Reply-To: <5f79c2c7-315b-409d-9f3d-78c1fb03bb49@sirena.org.uk>
From: Mark Brown [mailto:broonie@kernel.org]
Sent: Friday, July 14, 2023 10:21 PM
> On Fri, Jul 14, 2023 at 08:15:40PM +0000, Christoph Niedermaier wrote:
>>> On Fri, Jul 14, 2023 at 07:03:28PM +0000, Christoph Niedermaier wrote:
>
>>> The ones quoted above.
>
>> The kernel test robot wrote:
>> [...]
>> If you fix the issue, kindly add following tag where applicable
>> | Reported-by: kernel test robot <lkp@intel.com>
>> | Link: https://lore.kernel.org/oe-kbuild-all/202303082246.GuLdPL0t-lkp@intel.com/
>> [...]
>
>> Maybe that misled me.
>
> Yes, I wish it wouldn't do that. That really only applies when you're
> sending a patch that's substantially a fix for the issue it reports, for
> things that have not yet been applied it's just a normal review comment
> and you shouldn't add the tags.
Thank you for this clarification.
Regards
Christoph
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Support Opensource <support.opensource@diasemi.com>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
Liam Girdwood <lgirdwood@gmail.com>, Marek Vasut <marex@denx.de>,
kernel <kernel@dh-electronics.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH V5] regulator: da9062: Make the use of IRQ optional
Date: Fri, 14 Jul 2023 20:27:45 +0000 [thread overview]
Message-ID: <ef02362fdb5546e4962f1793659f2a54@dh-electronics.com> (raw)
In-Reply-To: <5f79c2c7-315b-409d-9f3d-78c1fb03bb49@sirena.org.uk>
From: Mark Brown [mailto:broonie@kernel.org]
Sent: Friday, July 14, 2023 10:21 PM
> On Fri, Jul 14, 2023 at 08:15:40PM +0000, Christoph Niedermaier wrote:
>>> On Fri, Jul 14, 2023 at 07:03:28PM +0000, Christoph Niedermaier wrote:
>
>>> The ones quoted above.
>
>> The kernel test robot wrote:
>> [...]
>> If you fix the issue, kindly add following tag where applicable
>> | Reported-by: kernel test robot <lkp@intel.com>
>> | Link: https://lore.kernel.org/oe-kbuild-all/202303082246.GuLdPL0t-lkp@intel.com/
>> [...]
>
>> Maybe that misled me.
>
> Yes, I wish it wouldn't do that. That really only applies when you're
> sending a patch that's substantially a fix for the issue it reports, for
> things that have not yet been applied it's just a normal review comment
> and you shouldn't add the tags.
Thank you for this clarification.
Regards
Christoph
next prev parent reply other threads:[~2023-07-14 20:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 9:03 [PATCH V5] regulator: da9062: Make the use of IRQ optional Christoph Niedermaier
2023-07-13 9:03 ` Christoph Niedermaier
2023-07-13 12:30 ` Mark Brown
2023-07-13 12:30 ` Mark Brown
2023-07-13 15:36 ` Christoph Niedermaier
2023-07-13 15:36 ` Christoph Niedermaier
2023-07-13 16:34 ` Mark Brown
2023-07-13 16:34 ` Mark Brown
2023-07-14 19:03 ` Christoph Niedermaier
2023-07-14 19:03 ` Christoph Niedermaier
2023-07-14 19:16 ` Mark Brown
2023-07-14 19:16 ` Mark Brown
2023-07-14 20:15 ` Christoph Niedermaier
2023-07-14 20:15 ` Christoph Niedermaier
2023-07-14 20:20 ` Mark Brown
2023-07-14 20:20 ` Mark Brown
2023-07-14 20:27 ` Christoph Niedermaier [this message]
2023-07-14 20:27 ` Christoph Niedermaier
2023-07-13 19:51 ` Mark Brown
2023-07-13 19:51 ` 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=ef02362fdb5546e4962f1793659f2a54@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=broonie@kernel.org \
--cc=kernel@dh-electronics.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.