[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZGHUjUpI-5JWNCAf@surfacebook>
Date: Mon, 15 May 2023 09:43:25 +0300
From: andy.shevchenko@...il.com
To: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Cc: Johan Hovold <johan@...nel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"brgl@...ev.pl" <brgl@...ev.pl>,
"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
"maz@...nel.org" <maz@...nel.org>,
Ben Brown <Ben.Brown@...iedtelesis.co.nz>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpiolib: Avoid side effects in gpio_is_visible()
Sun, May 14, 2023 at 09:57:58PM +0000, Chris Packham kirjoitti:
> On 12/05/23 19:24, Johan Hovold wrote:
> > On Fri, May 12, 2023 at 04:28:06PM +1200, Chris Packham wrote:
...
> > You need a better explanation as to why this is an issue. What does the
> > warning look like for example?
>
> Ironically I had that in my first attempt to address the issue but was
> told it was too much detail. So now I've gone too far the other way.
> I'll include it in the response I'm about to send to LinusW.
You have been (implicitly) told to reduce the scope of the details to have
the only important ones, removing the traceback completely wasn't on the
table.
Citation: "Besides the very noisy traceback in the commit message (read
https://kernel.org/doc/html/latest/process/submitting-patches.html#backtraces-in-commit-messages)"
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists