[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f79c2c7-315b-409d-9f3d-78c1fb03bb49@sirena.org.uk>
Date: Fri, 14 Jul 2023 21:20:32 +0100
From: Mark Brown <broonie@...nel.org>
To: Christoph Niedermaier <cniedermaier@...electronics.com>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Support Opensource <support.opensource@...semi.com>,
Adam Thomson <Adam.Thomson.Opensource@...semi.com>,
Liam Girdwood <lgirdwood@...il.com>,
Marek Vasut <marex@...x.de>,
kernel <kernel@...electronics.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V5] regulator: da9062: Make the use of IRQ optional
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@...el.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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists