linux-kernel - Re: [PATCH v3 0/4] gpio: sim, virtuser: minor usability enhancements

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: <173592172752.218872.9485472765451363107.b4-ty@linaro.org>
Date: Fri,  3 Jan 2025 17:28:49 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: linux-gpio@...r.kernel.org,
	Koichiro Den <koichiro.den@...onical.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	linus.walleij@...aro.org,
	brgl@...ev.pl,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/4] gpio: sim, virtuser: minor usability enhancements

From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>


On Fri, 03 Jan 2025 23:18:25 +0900, Koichiro Den wrote:
> This is just a minor usability enhancement proposal and some bug fixes for
> gpio-virtuser and gpio-sim.
> 
> Koichiro Den (4):
>   gpio: virtuser: fix missing lookup table cleanups
>   gpio: virtuser: fix handling of multiple conn_ids in lookup table
>   gpio: virtuser: lock up configfs that an instantiated device depends on
>   gpio: sim: lock up configfs that an instantiated device depends on
> 
> [...]

Applied, thanks!

[1/4] gpio: virtuser: fix missing lookup table cleanups
      commit: a619cba8c69c434258ff4101d463322cd63e1bdc
[2/4] gpio: virtuser: fix handling of multiple conn_ids in lookup table
      commit: 656cc2e892f128b03ea9ef19bd11d70f71d5472b
[3/4] gpio: virtuser: lock up configfs that an instantiated device depends on
      commit: c7c434c1dba955005f5161dae73f09c0a922cfa7
[4/4] gpio: sim: lock up configfs that an instantiated device depends on
      commit: 8bd76b3d3f3af7ac2898b6a27ad90c444fec418f

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>