linux-kernel - Re: [PULL REQUEST] i2c-for-6.16-rc3

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: <aFvAlSQICukBzt7K@shikoro>
Date: Wed, 25 Jun 2025 11:25:41 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Wolfram Sang <wsa@...nel.org>, linux-i2c@...r.kernel.org,
	linux-kernel@...r.kernel.org, Bartosz Golaszewski <brgl@...ev.pl>,
	Andi Shyti <andi.shyti@...nel.org>
Subject: Re: [PULL REQUEST] i2c-for-6.16-rc3

Linus,

> If you do conversions after the merge window, make them DAMN OBVIOUS.
> Make them minimal, make them automated, and DO NOT DO OTHER RANDOM
> CRAP AROUND THEM.

Okay, I don't want to do annoying things, so let me rephrase what I got
out of this. I should have 2 cleanup patches, one for the callback
changes and one for the whitespace changes?

Because I think the whitespace patch is needed. This is still the
beginning of a larger refactoring and having struct members initialized
according to coding style will greatly simplify next steps. And this
paragraph should then be the commit message of the whitespace patch.

I assumed that it was obvious that everything in this pull request was
automated. I honestly really don't enjoy pushing whitespaces around
manually.

   Wolfram

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)