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: <1f13c705-dec7-48f6-a6d7-4a9000eedf7d@app.fastmail.com>
Date: Fri, 14 Jun 2024 13:38:05 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: Uwe Kleine-König <u.kleine-koenig@...libre.com>,
 "Sean Young" <sean@...s.org>
Cc: linux-kernel@...r.kernel.org, linux-pwm@...r.kernel.org
Subject: Re: [PATCH] bus: ts-nbus: Use pwm_apply_might_sleep()

On Fri, Jun 14, 2024, at 12:06, Uwe Kleine-König wrote:
> On Fri, Jun 14, 2024 at 10:08:29AM +0100, Sean Young wrote:
>
> Thanks. I guess the patch becoming
> 8129d25e32b7fd0f77bc664252321f3a16bb26b8 was created a while before
> pwm_apply_might_sleep() was a thing.
>
> Acked-by: Uwe Kleine-König <u.kleine-koenig@...libre.com>
>
> Arnd, you merged the last changes to that driver. Do you want to care
> for that one, too? If not I can apply it via my pwm tree.

Whichever works best for you. I generally take drivers/bus
and drivers/soc fixes through the soc tree, but if this is
a PWM related change then having it in the pwm tree makes
sense as well.

If you like me to pick it up through the soc tree, please
forward the fix to soc@...nel.org.

      Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ