linux-kernel - Re: [PATCH] regmap: permit to set reg_update

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]

Date:   Mon, 18 Jul 2022 15:48:52 +0200
From:   Christian Marangi <ansuelsmth@...il.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     linux-kernel@...r.kernel.org, rafael@...nel.org,
        gregkh@...uxfoundation.org
Subject: Re: [PATCH] regmap: permit to set reg_update_bits with bulk
 implementation

On Mon, Jul 18, 2022 at 02:43:46PM +0100, Mark Brown wrote:
> On Fri, 15 Jul 2022 22:10:32 +0200, Christian Marangi wrote:
> > A regmap may still require to set a custom reg_update_bits instead of
> > relying to the regmap_bus_read/write general function.
> > 
> > Permit to set it in the map if provided by the regmap config.
> > 
> > 
> 
> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
> 
> Thanks!
> 
> [1/1] regmap: permit to set reg_update_bits with bulk implementation
>       commit: 739f872e48d47c97fa17a86a7b3356771b75240c
> 

Hi,
thanks, assuming everything went smooth with the merge to linux-next and
no problems arise, can you provide a signed tag?

This is needed for a net-next series that is currently in RFC state as
it does depends on this.

(I had this problem before and it was said that in this kind of
situation I had to ask for a signed tag to merge the related patch in
net-next branch)

Thanks for the help!

-- 
	Ansuel