linux-kernel - Re: [PATCH v3] gpio: dwapb: mask/unmask IRQ when disable/enale it

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <yko4bwzrnlvncljpgyxlsvioqeyf3zxb255qexlawooqjxvedn@dkr7i7fame3n>
Date: Wed, 20 Dec 2023 00:58:16 +0300
From: Serge Semin <fancer.lancer@...il.com>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>, 
	xiongxin <xiongxin@...inos.cn>, Andy Shevchenko <andy@...nel.org>, hoan@...amperecomputing.com, 
	linus.walleij@...aro.org, brgl@...ev.pl, linux-gpio@...r.kernel.org, 
	linux-kernel@...r.kernel.org, stable@...nel.org, Riwen Lu <luriwen@...inos.cn>
Subject: Re: [PATCH v3] gpio: dwapb: mask/unmask IRQ when disable/enale it

Hi Konstantin

On Tue, Dec 19, 2023 at 01:56:47PM -0500, Konstantin Ryabitsev wrote:
> On Tue, Dec 19, 2023 at 05:31:38PM +0300, Serge Semin wrote:
> > > > Also note all the tags you've already got must be preserved on the
> > > > next patch revisions. One more time:
> > > 
> > > > Acked-by: Serge Semin <fancer.lancer@...il.com>
> > > 
> > > I recommend using `b4` for that.
> > > 
> > > it harvests tags from the email thread, so no need to care about
> > > possible misses.
> > 
> > AFAICS it doesn't pick up the tags from the previous revisions at
> > least if the new patch wasn't submitted as in-reply-to the prev one.
> 

> It's a known limitation at this time, but it will be improved in the near
> future and we'll be able to grab trailers across revisions as long as the
> patch-id remains the same.

Ok. Thanks for the note.

I am sure you are well aware of that, but in some cases the tags are
intentionally omitted in the new patch revisions for instance due to
significant patch body change. How are you going to handle that? Just
make the tags picking up optional? Perhaps making the tags handling
interactive with printing a text/context around the tag?

-Serge(y)

> 
> -K