public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "jroedel@suse.de" <jroedel@suse.de>
To: Qian Cai <cai@lca.pw>
Cc: Gary R Hook <ghook@amd.com>, "Hook, Gary" <Gary.Hook@amd.com>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iommu/amd: print out "tag" in INVALID_PPR_REQUEST
Date: Tue, 28 May 2019 15:37:42 +0200	[thread overview]
Message-ID: <20190528133742.GA8151@suse.de> (raw)
In-Reply-To: <1557845746.6132.27.camel@lca.pw>

On Tue, May 14, 2019 at 10:55:46AM -0400, Qian Cai wrote:
> Jroedel, I am wondering what the plan for 41e59a41fc5d1 (iommu tree) or this
> patch to be pushed to the linux-next or mainline...

Looks like I applied that patch directly to the master branch, which is
not what goes upstream. I cherry-picked it to x86/amd, so it will go
upstream for v5.3.


Regards,

	Joerg

      reply	other threads:[~2019-05-28 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06  4:11 [PATCH] iommu/amd: print out "tag" in INVALID_PPR_REQUEST Qian Cai
2019-05-07 13:47 ` Gary R Hook
2019-05-14 14:55   ` Qian Cai
2019-05-28 13:37     ` jroedel [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=20190528133742.GA8151@suse.de \
    --to=jroedel@suse.de \
    --cc=Gary.Hook@amd.com \
    --cc=cai@lca.pw \
    --cc=ghook@amd.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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