On Thu, Oct 20, 2022 at 3:13 PM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Thu, 20 Oct 2022 10:24:51 -0600 "Jason A. Donenfeld" <Jason@xxxxxxxxx> wrote: > > > Hi Andrew, > > > > On Wed, Oct 19, 2022 at 6:03 PM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > The patch titled > > > Subject: kbuild: treat char as always unsigned > > > has been added to the -mm mm-nonmm-unstable branch. Its filename is > > > kbuild-treat-char-as-always-unsigned.patch > > > > > > This patch will shortly appear at > > > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/kbuild-treat-char-as-always-unsigned.patch > > > > > > This patch will later appear in the mm-nonmm-unstable branch at > > > git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm > > > > Looks like you missed this email - > > https://lore.kernel.org/lkml/Y1CP%2FuJb1SQjyS0n@xxxxxxxxx/ > > I saw that email after I'd merged it. > > > didn't communicate about your intention to take this. Kind of > > annoying, but oh well. Either way, I'll drop it from my tree, so that > > -next has a clear path with it. Just please don't drop it from your > > tree without appropriate discussion first. As mentioned in the thread, > > there inevitably will be a few dragons with this patch, and the whole > > idea of putting this in -next a whopping 4.5 months before 6.2 is > > released is so that we can actually have time to chip away at those > > issues as they come up. So please don't drop this at the very first > > sign of trouble; just plan for some trouble. > > No, please go ahead and merge it in your tree (I didn't actually know > you ran a tree). Once it appears in -next, Stephen will tell us and > I'll drop my copy. This happens fairly commonly. Okay, will do. Jason
