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] [day] [month] [year] [list]
Message-ID: <810af0b9-aa21-4f11-9708-92c870615cc8@gmail.com>
Date: Tue, 7 Jan 2025 01:31:02 +0100
From: Raphaël Gallais-Pou <rgallaispou@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Patrice Chotard <patrice.chotard@...s.st.com>,
 Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Adrian Hunter <adrian.hunter@...el.com>, Ulf Hansson
 <ulf.hansson@...aro.org>, Miquel Raynal <miquel.raynal@...tlin.com>,
 Richard Weinberger <richard@....at>, Vignesh Raghavendra <vigneshr@...com>,
 Damien Le Moal <dlemoal@...nel.org>, Niklas Cassel <cassel@...nel.org>,
 Alexandre Torgue <alexandre.torgue@...s.st.com>,
 Jose Abreu <joabreu@...opsys.com>, Andrew Lunn <andrew+netdev@...n.ch>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 Maxime Coquelin <mcoquelin.stm32@...il.com>,
 linux-arm-kernel@...ts.infradead.org, linux-usb@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org,
 linux-mtd@...ts.infradead.org, linux-ide@...r.kernel.org,
 netdev@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
 linux-spi@...r.kernel.org
Subject: Re: [PATCH 0/6] Switch from CONFIG_PM_SLEEP guards to pm_sleep_ptr()



Le 06/01/2025 à 14:08, Mark Brown a écrit :
> On Sun, Dec 29, 2024 at 12:32:39AM +0100, Raphael Gallais-Pou wrote:
>> Prevent the use of macros, and rely instead on kernel configuration for
>> power management.
>>
>> This series makes the same change over six different drivers:
>> usb-st-dwc3, sdhci-st, st-spi-fsm, ahci_st, sti-dwmac, spi-st.
> 
> Is there any actual interaction between these changes?  In general you
> shouldn't combine patches for multiple subsystems into a single series
> unless there's some dependency or other interaction since it just
> complicates management of the patches.

Hi,

No, there isn't apart from the fact that those are stm32 drivers. As 
Miquel also stated a few days ago, is was wrong for me to sent all of 
this in a whole serie. I will just resend them separately as a v2, 
taking into account Miquel's review[1] and the kernel robot.

Regards,
Raphaël


[1] https://lore.kernel.org/lkml/877c7ha77n.fsf@bootlin.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ