linux-kernel - Re: i2c-host for v6.18

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: <5sisddiomyxmkvm744h5luphomyadnenpjk5pf5kemqw7tcok3@qzmbc2cr42vw>
Date: Sat, 6 Dec 2025 00:14:49 +0100
From: Andi Shyti <andi.shyti@...nel.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: linux-i2c <linux-i2c@...r.kernel.org>, 
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: i2c-host for v6.18

Hi Wolfram,

> >   Linux 6.18 (2025-11-30 14:42:10 -0800)
> 
> Urgs, but this is highly problematic. I can't pull something based on
> 6.18. Usually, things are based on -rc1 or something early to show Linus
> that it has been in -next for a while. He won't pull something that is
> less than 48 hours in public and so won't I.

Just a note that I merged the last few patches on Wednesday. So,
if the 48 hour window applies, we are well within it.

> I hope you still have the ref of the branch *before* you rebased to
> 6.18. Please send a pull request for this old one.

As I mentioned privately, I can split this into two pull requests
and use the older reference for the earlier patches if that
helps. To me it feels more like a formality, since those patches
have already been in -next for a few weeks and were only rebased
on top of v6.18. But I am happy to do whatever you prefer.

Andi