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: <20260126101308.TOAFAQsM@linutronix.de>
Date: Mon, 26 Jan 2026 11:13:08 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, linux-rt-devel@...ts.linux.dev,
	Thomas Gleixner <tglx@...nel.org>, Lee Jones <lee@...nel.org>,
	patches@...nsource.cirrus.com, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH 17/21] mfd: wm8350-core: Use IRQF_ONESHOT

On 2026-01-26 12:05:13 [+0200], Andy Shevchenko wrote:
> > or will be imported via git-am.
> 
> Yes, that's the idea. `git am` will strip them out. But why would you need to
> apply via `git am` locally? You can pull from the tree.

I fetch from the list to pick up the tags, fix some of them up as the
iio but most of them remain the same. Then I post the v2. Where do I get
the Cc from? So I add them manually again?

> > If you continue to nitpick here, I could do it for the next iio
> > submission assuming it will be picked-up by iio maintainers. But doing
> > it just for the single mfd patch looks like too much work.
> 
> I'm thinking of all the patches.
> 

Sebastian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ