linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lan Tianyu <Tianyu.Lan@microsoft.com>
Subject: Re: linux-next: manual merge of the vhost tree with the iommu tree
Date: Mon, 27 May 2019 11:16:06 -0400	[thread overview]
Message-ID: <20190527111543-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190527092718.GC21613@8bytes.org>

On Mon, May 27, 2019 at 11:27:18AM +0200, Joerg Roedel wrote:
> On Sun, May 12, 2019 at 01:16:26PM -0400, Michael S. Tsirkin wrote:
> > Joerg, what are we doing with these patches?
> > It was tested in next with no bad effects.
> > I sent an ack - do you want to pick it up?
> > Or have me include it in my pull?
> 
> I'd prefer it in my tree, if you are fine with the spec.
> 
> Regards,
> 
> 	Joerg

OK let me just check spec status.

-- 
MST

      reply	other threads:[~2019-05-27 15:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27  4:25 linux-next: manual merge of the vhost tree with the iommu tree Stephen Rothwell
2019-02-27 11:30 ` Jean-Philippe Brucker
2019-02-27 13:58   ` Michael S. Tsirkin
2019-02-28 10:04     ` Joerg Roedel
2019-05-12 17:16       ` Michael S. Tsirkin
2019-05-13 14:29         ` Jean-Philippe Brucker
2019-05-27  9:27         ` Joerg Roedel
2019-05-27 15:16           ` Michael S. Tsirkin [this message]

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=20190527111543-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=Tianyu.Lan@microsoft.com \
    --cc=jean-philippe.brucker@arm.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).