[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1ayyS/7b5qnySi3@zx2c4.com>
Date: Mon, 24 Oct 2022 17:44:09 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@...il.com>, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, mm-commits@...r.kernel.org,
masahiroy@...nel.org, keescook@...omium.org,
gregkh@...uxfoundation.org, andriy.shevchenko@...ux.intel.com,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH -mm] -funsigned-char, x86: make struct
p4_event_bind::cntr signed array
On Thu, Oct 20, 2022 at 11:33:39AM -0600, Jason A. Donenfeld wrote:
> Hi Linus,
>
> On Thu, Oct 20, 2022 at 11:15 AM Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> > Can we please try to collect these all in one place?
> >
> > I see that Andrew picked up the original one for -mm, but I think it
> > would be better if we had one specific place for all of this (one
> > branch) to collect it all.
>
> Sure. Andrew can drop it from -mm, and I'll collect everything in:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/linux.git/log/?h=unsigned-char&r
>
> And I'll ask Stephen to add that branch to -next.
So, as discussed, I'm doing this, and it's in -next now. And as a
result, we're getting warnings and such that I am fixing one by one.
Progress, good.
But it occurs to me that most of these bugs are not in
architecture-specific code like the x86 p4_event_bind one from last
week. That means I'll be submitting these as *fixes* during 6.1, since
they're broken on some architecture already, rather than waiting to
submit them to you via my unsigned-char tree in 6.2.
Just FYI.
Jason
Powered by blists - more mailing lists