From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mgurtovoy@nvidia.com, lingshan.zhu@intel.com,
KVM list <kvm@vger.kernel.org>,
xianting.tian@linux.alibaba.com, Netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Wolfram Sang <wsa@kernel.org>,
xieyongji@bytedance.com, Viresh Kumar <viresh.kumar@linaro.org>,
arseny.krasnov@kaspersky.com, Will Deacon <will@kernel.org>,
elic@nvidia.com
Subject: Re: [GIT PULL] virtio,vdpa,vhost: features, fixes
Date: Sat, 11 Sep 2021 20:11:00 -0400 [thread overview]
Message-ID: <20210911200508-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=wgcXzshPVvVgGDqa9Y9Sde6RsUvj9jvx0htBqPuaTGX4Q@mail.gmail.com>
On Sat, Sep 11, 2021 at 02:56:12PM -0700, Linus Torvalds wrote:
> So you are hereby put on notice: next time I get this kind of
> half-arsed garbage pull request, I won't spend the energy on trying to
> figure out what is actually going on. I will just throw it in the
> trash.
>
> Because honestly, that's where this pull request belonged.
>
> Linus
OK so I was worrying about these patches anyway, and that
is why I put them on top. So I just sent GIT PULL V2 which
includes all the same commits except for the last 13 patches,
so they all have been in linux-next.
It's in the tag for_linus_v2 - the point of keeping for_linus
intact was so anyone can compare these two.
Hope that clarifies rather than confuses things even more.
Mea culpa, etc.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: KVM list <kvm@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arseny.krasnov@kaspersky.com, caihuoqing@baidu.com,
elic@nvidia.com, Jason Wang <jasowang@redhat.com>,
lingshan.zhu@intel.com, mgurtovoy@nvidia.com,
Viresh Kumar <viresh.kumar@linaro.org>,
Will Deacon <will@kernel.org>, Wolfram Sang <wsa@kernel.org>,
xianting.tian@linux.alibaba.com, xieyongji@bytedance.com
Subject: Re: [GIT PULL] virtio,vdpa,vhost: features, fixes
Date: Sat, 11 Sep 2021 20:11:00 -0400 [thread overview]
Message-ID: <20210911200508-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=wgcXzshPVvVgGDqa9Y9Sde6RsUvj9jvx0htBqPuaTGX4Q@mail.gmail.com>
On Sat, Sep 11, 2021 at 02:56:12PM -0700, Linus Torvalds wrote:
> So you are hereby put on notice: next time I get this kind of
> half-arsed garbage pull request, I won't spend the energy on trying to
> figure out what is actually going on. I will just throw it in the
> trash.
>
> Because honestly, that's where this pull request belonged.
>
> Linus
OK so I was worrying about these patches anyway, and that
is why I put them on top. So I just sent GIT PULL V2 which
includes all the same commits except for the last 13 patches,
so they all have been in linux-next.
It's in the tag for_linus_v2 - the point of keeping for_linus
intact was so anyone can compare these two.
Hope that clarifies rather than confuses things even more.
Mea culpa, etc.
--
MST
next prev parent reply other threads:[~2021-09-12 0:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 13:56 [GIT PULL] virtio,vdpa,vhost: features, fixes Michael S. Tsirkin
2021-09-09 13:56 ` Michael S. Tsirkin
2021-09-11 21:56 ` Linus Torvalds
2021-09-11 21:56 ` Linus Torvalds
2021-09-11 23:51 ` Yongji Xie
2021-09-12 0:11 ` Michael S. Tsirkin [this message]
2021-09-12 0:11 ` Michael S. Tsirkin
2021-09-12 0:43 ` Linus Torvalds
2021-09-12 0:43 ` Linus Torvalds
2021-09-12 0:42 ` pr-tracker-bot
2021-09-12 0:42 ` 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=20210911200508-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arseny.krasnov@kaspersky.com \
--cc=elic@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=will@kernel.org \
--cc=wsa@kernel.org \
--cc=xianting.tian@linux.alibaba.com \
--cc=xieyongji@bytedance.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.