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
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: bobby.eshleman@bytedance.com, kvm@vger.kernel.org,
sunnanyong@huawei.com, yuancan@huawei.com,
virtualization@lists.linux-foundation.org,
weiyongjun1@huawei.com, elic@nvidia.com, set_pte_at@outlook.com,
m.szyprowski@samsung.com, almasrymina@google.com,
sfr@canb.auug.org.au, dave@stgolabs.net,
anders.roxell@linaro.org, lulu@redhat.com, ruanjinjie@huawei.com,
rafaelmendsr@gmail.com, pizhenwei@bytedance.com,
eperezma@redhat.com, angus.chen@jaguarmicro.com, lkft@linaro.org,
colin.i.king@gmail.com, sammler@google.com, nathan@kernel.org,
leiyang@redhat.com, harshit.m.mogalapalli@oracle.com,
wangjianli@cdjrlc.com, gautam.dawar@xilinx.com,
pabeni@redhat.com, dengshaomin@cdjrlc.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, dmitry.fomichev@wdc.com,
wangrong68@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
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-12-24 11:29 UTC|newest]
Thread overview: 21+ 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-22 19:43 ` Michael S. Tsirkin
2022-12-23 19:54 ` Linus Torvalds
2022-12-23 19:54 ` Linus Torvalds
2022-12-23 22:27 ` Michael S. Tsirkin
2022-12-23 22:27 ` Michael S. Tsirkin
2022-12-23 22:35 ` Michael S. Tsirkin
2022-12-23 22:35 ` Michael S. Tsirkin
2022-12-23 22:36 ` Linus Torvalds
2022-12-23 22:36 ` Linus Torvalds
2022-12-24 5:35 ` Michael S. Tsirkin
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 6:10 ` Linus Torvalds
2022-12-24 11:28 ` Michael S. Tsirkin [this message]
2022-12-24 11:28 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2023-04-24 21:48 Michael S. Tsirkin
2023-04-24 21:48 ` Michael S. Tsirkin
2023-04-28 0:31 ` pr-tracker-bot
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.com \
--cc=almasrymina@google.com \
--cc=alvaro.karsz@solid-run.com \
--cc=anders.roxell@linaro.org \
--cc=angus.chen@jaguarmicro.com \
--cc=bobby.eshleman@bytedance.com \
--cc=colin.i.king@gmail.com \
--cc=dave@stgolabs.net \
--cc=dengshaomin@cdjrlc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=elic@nvidia.com \
--cc=eperezma@redhat.com \
--cc=gautam.dawar@xilinx.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=leiyang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=lulu@redhat.com \
--cc=m.szyprowski@samsung.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=rafaelmendsr@gmail.com \
--cc=ricardo.canuelo@collabora.com \
--cc=ruanjinjie@huawei.com \
--cc=sammler@google.com \
--cc=set_pte_at@outlook.com \
--cc=sfr@canb.auug.org.au \
--cc=sgarzare@redhat.com \
--cc=shaoqin.huang@intel.com \
--cc=si-wei.liu@oracle.com \
--cc=stable@vger.kernel.org \
--cc=stefanha@gmail.com \
--cc=sunnanyong@huawei.com \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wangjianli@cdjrlc.com \
--cc=wangrong68@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yuancan@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.