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: <173316099054.156347.17424661167771006214.b4-ty@kernel.org>
Date: Mon, 02 Dec 2024 17:36:30 +0000
From: Mark Brown <broonie@...nel.org>
To: Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org, 
 llvm@...ts.linux.dev, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 "Rafael J. Wysocki" <rafael@...nel.org>, 
 Nathan Chancellor <nathan@...nel.org>, 
 Nick Desaulniers <ndesaulniers@...gle.com>, 
 Bill Wendling <morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>
Subject: Re: [PATCH v1 0/3] regmap: Cleanup and microoptimization

On Thu, 21 Nov 2024 12:57:20 +0200, Andy Shevchenko wrote:
> Two patches move the code to use BITS_TO_BYTES(), while the last
> one otpimizes the code generation on x86 (32- and 64-bit on different
> compilers).
> 
> Andy Shevchenko (3):
>   regmap: cache: Use BITS_TO_BYTES()
>   regmap: Use BITS_TO_BYTES()
>   regmap: place foo / 8 and foo % 8 closer to each other
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/3] regmap: cache: Use BITS_TO_BYTES()
      commit: 4a3aafe01f6c628932a402c21e58101173c8dab3
[2/3] regmap: Use BITS_TO_BYTES()
      commit: a4a7d86bc1a59839ad0dffbefa473135b342dd0b
[3/3] regmap: place foo / 8 and foo % 8 closer to each other
      commit: 9b3cd5c7099fe7710356dd76ecf9910dc8c32548

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ