Michael S. Tsirkin
2022-Dec-24 05:35 UTC
[GIT PULL] virtio,vhost,vdpa: features, fixes, cleanups
On Fri, Dec 23, 2022 at 02:36:46PM -0800, Linus Torvalds wrote:> On Fri, Dec 23, 2022 at 2:27 PM Michael S. Tsirkin <mst at redhat.com> wrote: > > > > They were all there, just not as these commits, as I squashed fixups to > > avoid bisect breakages with some configs. Did I do wrong? > > I am literally looking at the next-20221214 state right now, doing > > git log linus/master.. -- drivers/vhost/vsock.c > git log linus/master.. -- drivers/vdpa/mlx5/ > git log --grep="temporary variable type tweak" > > and seeing nothing. > > So none of these commits - in *any* form - were in linux-next last > week as far as I can tell. > > LinusThey were in next-20221220 though. -- MST
Linus Torvalds
2022-Dec-24 06:10 UTC
[GIT PULL] virtio,vhost,vdpa: features, fixes, cleanups
On Fri, Dec 23, 2022 at 9:35 PM Michael S. Tsirkin <mst at redhat.com> wrote:> > They were in next-20221220 though.So, perfect for the *next* merge window. Do you understand what the word "next" means? We don't call it "linux-this", do we? This is not a new rule. Things are supposed to be ready *before* the merge window (that's what makes it "next", get it?). I will also point you to to https://lore.kernel.org/lkml/CAHk-=wj_HcgFZNyZHTLJ7qC2613zphKDtLh6ndciwopZRfH0aQ at mail.gmail.com/ where I'm being pretty damn clear about things. And before you start bleating about "I needed more heads up", never mind that this isn't even a new rule, and never mind what that "next" word means, let me just point to the 6.1-rc6 notice too: https://lore.kernel.org/lkml/CAHk-=wgUZwX8Sbb8Zvm7FxWVfX6CGuE7x+E16VKoqL7Ok9vv7g at mail.gmail.com/ and if the meaning of "next" has eluded you all these years, maybe it was high time you learnt. Hmm? Linus