All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: hulkci@huawei.com, matej.genci@nutanix.com,
	KVM list <kvm@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Netdev <netdev@vger.kernel.org>,
	yanaijie@huawei.com, YueHaibing <yuehaibing@huawei.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	ashutosh.dixit@intel.com, eperezma@redhat.com,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	eli@mellanox.com, Stephen Rothwell <sfr@canb.auug.org.au>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Markus Elfring <elfring@users.sourceforge.net>
Subject: Re: [GIT PULL] vhost: cleanups and fixes
Date: Thu, 16 Apr 2020 08:20:44 -0400	[thread overview]
Message-ID: <20200416081330-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=wgVQcD=JJVmowEorHHQSVmSw+vG+Ddc4FATZoTp9mfUmw@mail.gmail.com>

On Wed, Apr 15, 2020 at 05:46:33PM -0700, Linus Torvalds wrote:
> On Tue, Apr 14, 2020 at 9:36 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > virtio: fixes, cleanups
> 
> Looking at this, about 75% of it looks like it should have come in
> during the merge window, not now.
> 
>               Linus

Well it's all just fallout from

	commit 61b89f23f854f458b8e23719978df58260f051ed
	Author: Michael S. Tsirkin <mst@redhat.com>
	Date:   Mon Apr 6 08:42:55 2020 -0400

	    vhost: force spec specified alignment on types

which I didn't know we need until things landed upstream and
people started testing with weird configs.

That forced changes to a header file and the rest followed.

We could just ignore -mabi=apcs-gnu build being broken for this release -
is that preferable? Pls let me know.

-- 
MST

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>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	ashutosh.dixit@intel.com,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Markus Elfring <elfring@users.sourceforge.net>,
	eli@mellanox.com, eperezma@redhat.com,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	hulkci@huawei.com, "Cc: stable@vger.kernel.org, david@redhat.com,
	dverkamp@chromium.org, hch@lst.de, jasowang@redhat.com,
	liang.z.li@intel.com, mst@redhat.com,
	tiny.windzz@gmail.com," <jasowang@redhat.com>,
	matej.genci@nutanix.com, Stephen Rothwell <sfr@canb.auug.org.au>,
	yanaijie@huawei.com, YueHaibing <yuehaibing@huawei.com>
Subject: Re: [GIT PULL] vhost: cleanups and fixes
Date: Thu, 16 Apr 2020 08:20:44 -0400	[thread overview]
Message-ID: <20200416081330-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=wgVQcD=JJVmowEorHHQSVmSw+vG+Ddc4FATZoTp9mfUmw@mail.gmail.com>

On Wed, Apr 15, 2020 at 05:46:33PM -0700, Linus Torvalds wrote:
> On Tue, Apr 14, 2020 at 9:36 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > virtio: fixes, cleanups
> 
> Looking at this, about 75% of it looks like it should have come in
> during the merge window, not now.
> 
>               Linus

Well it's all just fallout from

	commit 61b89f23f854f458b8e23719978df58260f051ed
	Author: Michael S. Tsirkin <mst@redhat.com>
	Date:   Mon Apr 6 08:42:55 2020 -0400

	    vhost: force spec specified alignment on types

which I didn't know we need until things landed upstream and
people started testing with weird configs.

That forced changes to a header file and the rest followed.

We could just ignore -mabi=apcs-gnu build being broken for this release -
is that preferable? Pls let me know.

-- 
MST


  reply	other threads:[~2020-04-16 12:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 16:36 [GIT PULL] vhost: cleanups and fixes Michael S. Tsirkin
2020-04-14 16:36 ` Michael S. Tsirkin
2020-04-16  0:46 ` Linus Torvalds
2020-04-16  0:46   ` Linus Torvalds
2020-04-16 12:20   ` Michael S. Tsirkin [this message]
2020-04-16 12:20     ` Michael S. Tsirkin
2020-04-16 17:01     ` Linus Torvalds
2020-04-16 17:01       ` Linus Torvalds
2020-04-16 21:58       ` Michael S. Tsirkin
  -- strict thread matches above, loose matches on Subject: below --
2021-03-18 18:11 Michael S. Tsirkin
2021-03-18 18:11 ` Michael S. Tsirkin
2021-03-18 18:24 ` pr-tracker-bot
2021-03-18 18:24   ` pr-tracker-bot
2021-12-12 22:59 Michael S. Tsirkin
2021-12-12 22:59 ` Michael S. Tsirkin
2021-12-12 23:01 ` Michael S. Tsirkin
2021-12-12 23:01   ` Michael S. Tsirkin
2021-12-13 22:49 ` pr-tracker-bot
2021-12-13 22:49   ` 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=20200416081330-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=ashutosh.dixit@intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=elfring@users.sourceforge.net \
    --cc=eli@mellanox.com \
    --cc=eperezma@redhat.com \
    --cc=gustavo@embeddedor.com \
    --cc=hulkci@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matej.genci@nutanix.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=yanaijie@huawei.com \
    --cc=yuehaibing@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.