netdev - Re: [GIT PULL] virtio,vhost,vdpa: features, fixes, cleanups

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20221224061932-mutt-send-email-mst@kernel.org>
Date:   Sat, 24 Dec 2022 06:28:15 -0500
From:   "Michael S. Tsirkin" <mst@...hat.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        almasrymina@...gle.com, alvaro.karsz@...id-run.com,
        anders.roxell@...aro.org, angus.chen@...uarmicro.com,
        bobby.eshleman@...edance.com, colin.i.king@...il.com,
        dave@...olabs.net, dengshaomin@...rlc.com, dmitry.fomichev@....com,
        elic@...dia.com, eperezma@...hat.com, gautam.dawar@...inx.com,
        harshit.m.mogalapalli@...cle.com, jasowang@...hat.com,
        leiyang@...hat.com, lingshan.zhu@...el.com, lkft@...aro.org,
        lulu@...hat.com, m.szyprowski@...sung.com, nathan@...nel.org,
        pabeni@...hat.com, pizhenwei@...edance.com, rafaelmendsr@...il.com,
        ricardo.canuelo@...labora.com, ruanjinjie@...wei.com,
        sammler@...gle.com, set_pte_at@...look.com, sfr@...b.auug.org.au,
        sgarzare@...hat.com, shaoqin.huang@...el.com,
        si-wei.liu@...cle.com, stable@...r.kernel.org, stefanha@...il.com,
        sunnanyong@...wei.com, wangjianli@...rlc.com,
        wangrong68@...wei.com, weiyongjun1@...wei.com,
        xuanzhuo@...ux.alibaba.com, yuancan@...wei.com
Subject: Re: [GIT PULL] virtio,vhost,vdpa: features, fixes, cleanups

On Fri, Dec 23, 2022 at 10:10:30PM -0800, Linus Torvalds wrote:
> On Fri, Dec 23, 2022 at 9:35 PM Michael S. Tsirkin <mst@...hat.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@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@mail.gmail.com/
> 
> and if the meaning of "next" has eluded you all these years, maybe it
> was high time you learnt. Hmm?
> 
>               Linus

Yea I really screwed up with this one. High time I learned that "no
fallout from testing" most likely does not mean "no bugs" but instead
"you forgot to push to next". Putting procedures in place now to
check automatically.


-- 
MST