From: "Michael S. Tsirkin" <mst@redhat•com>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: kvm@vger•kernel.org, virtualization@lists•linux-foundation.org,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
almasrymina@google•com, alvaro.karsz@solid-run•com,
anders.roxell@linaro•org, angus.chen@jaguarmicro•com,
bobby.eshleman@bytedance•com, colin.i.king@gmail•com,
dave@stgolabs•net, dengshaomin@cdjrlc•com,
dmitry.fomichev@wdc•com, elic@nvidia•com, eperezma@redhat•com,
gautam.dawar@xilinx•com, harshit.m.mogalapalli@oracle•com,
jasowang@redhat•com, leiyang@redhat•com, lingshan.zhu@intel•com,
lkft@linaro•org, lulu@redhat•com, m.szyprowski@samsung•com,
nathan@kernel•org, pabeni@redhat•com, pizhenwei@bytedance•com,
rafaelmendsr@gmail•com, ricardo.canuelo@collabora•com,
ruanjinjie@huawei•com, sammler@google•com,
set_pte_at@outlook•com, sfr@canb•auug.org.au,
sgarzare@redhat•com, shaoqin.huang@intel•com,
si-wei.liu@oracle•com, stable@vger•kernel.org,
stefanha@gmail•com, sunnanyong@huawei•com, wangjianli@cdjrlc•com,
wangrong68@huawei•com, weiyongjun1@huawei•com,
xuanzhuo@linux•alibaba.com, yuancan@huawei•com
Subject: Re: [GIT PULL] virtio,vhost,vdpa: features, fixes, cleanups
Date: Sat, 24 Dec 2022 06:28:15 -0500 [thread overview]
Message-ID: <20221224061932-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=wh_cyzZgYp1pL8MDA6sioB1RndQ_fref=9V+vm9faE7fg@mail.gmail.com>
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@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@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
next prev parent reply other threads:[~2022-12-24 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 19:43 [GIT PULL] virtio,vhost,vdpa: features, fixes, cleanups Michael S. Tsirkin
2022-12-23 19:54 ` Linus Torvalds
2022-12-23 22:27 ` Michael S. Tsirkin
2022-12-23 22:35 ` Michael S. Tsirkin
2022-12-23 22:36 ` Linus Torvalds
2022-12-24 5:35 ` Michael S. Tsirkin
2022-12-24 5:49 ` Slade Watkins
2022-12-24 6:10 ` Linus Torvalds
2022-12-24 11:28 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-24 21:48 Michael S. Tsirkin
2023-04-28 0:31 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221224061932-mutt-send-email-mst@kernel.org \
--to=mst@redhat$(echo .)com \
--cc=almasrymina@google$(echo .)com \
--cc=alvaro.karsz@solid-run$(echo .)com \
--cc=anders.roxell@linaro$(echo .)org \
--cc=angus.chen@jaguarmicro$(echo .)com \
--cc=bobby.eshleman@bytedance$(echo .)com \
--cc=colin.i.king@gmail$(echo .)com \
--cc=dave@stgolabs$(echo .)net \
--cc=dengshaomin@cdjrlc$(echo .)com \
--cc=dmitry.fomichev@wdc$(echo .)com \
--cc=elic@nvidia$(echo .)com \
--cc=eperezma@redhat$(echo .)com \
--cc=gautam.dawar@xilinx$(echo .)com \
--cc=harshit.m.mogalapalli@oracle$(echo .)com \
--cc=jasowang@redhat$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=leiyang@redhat$(echo .)com \
--cc=lingshan.zhu@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lkft@linaro$(echo .)org \
--cc=lulu@redhat$(echo .)com \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=nathan@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pizhenwei@bytedance$(echo .)com \
--cc=rafaelmendsr@gmail$(echo .)com \
--cc=ricardo.canuelo@collabora$(echo .)com \
--cc=ruanjinjie@huawei$(echo .)com \
--cc=sammler@google$(echo .)com \
--cc=set_pte_at@outlook$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sgarzare@redhat$(echo .)com \
--cc=shaoqin.huang@intel$(echo .)com \
--cc=si-wei.liu@oracle$(echo .)com \
--cc=stable@vger$(echo .)kernel.org \
--cc=stefanha@gmail$(echo .)com \
--cc=sunnanyong@huawei$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=virtualization@lists$(echo .)linux-foundation.org \
--cc=wangjianli@cdjrlc$(echo .)com \
--cc=wangrong68@huawei$(echo .)com \
--cc=weiyongjun1@huawei$(echo .)com \
--cc=xuanzhuo@linux$(echo .)alibaba.com \
--cc=yuancan@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox