All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Jussi Maki <joamaki@gmail.com>
Subject: Re: [PATCH] iommu/amd: Tidy up DMA ops init
Date: Fri, 4 Jun 2021 18:35:17 +0100	[thread overview]
Message-ID: <781da5b3-4856-9a76-d803-51800dec6033@arm.com> (raw)
In-Reply-To: <YLpGHx+rYnBF64Yh@8bytes.org>

On 2021-06-04 16:26, Joerg Roedel wrote:
> On Thu, Jun 03, 2021 at 02:48:21PM +0100, Robin Murphy wrote:
>> As discussed on the report thread, I think it makes most sense to merge
>> this as a fix for 5.13 and not worry about any backporting.
>>
>>   drivers/iommu/amd/amd_iommu.h |  2 --
>>   drivers/iommu/amd/init.c      |  5 -----
>>   drivers/iommu/amd/iommu.c     | 31 +++++++++++++------------------
>>   3 files changed, 13 insertions(+), 25 deletions(-)
> 
> Applied for v5.13, thanks Robin et al for the quick work on this
> regression.
> 
> Robin, do you by chance have a Fixes tag which I can add?

For the sake of justifying this as "fix" rather than "cleanup", you may 
as well use the flush queue commit cited in the patch log - I maintain 
there's nothing technically wrong with that commit itself, but it is the 
point at which the underlying issue becomes worth fixing due to how they 
interact ;)

Cheers,
Robin.

WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Jussi Maki <joamaki@gmail.com>
Subject: Re: [PATCH] iommu/amd: Tidy up DMA ops init
Date: Fri, 4 Jun 2021 18:35:17 +0100	[thread overview]
Message-ID: <781da5b3-4856-9a76-d803-51800dec6033@arm.com> (raw)
In-Reply-To: <YLpGHx+rYnBF64Yh@8bytes.org>

On 2021-06-04 16:26, Joerg Roedel wrote:
> On Thu, Jun 03, 2021 at 02:48:21PM +0100, Robin Murphy wrote:
>> As discussed on the report thread, I think it makes most sense to merge
>> this as a fix for 5.13 and not worry about any backporting.
>>
>>   drivers/iommu/amd/amd_iommu.h |  2 --
>>   drivers/iommu/amd/init.c      |  5 -----
>>   drivers/iommu/amd/iommu.c     | 31 +++++++++++++------------------
>>   3 files changed, 13 insertions(+), 25 deletions(-)
> 
> Applied for v5.13, thanks Robin et al for the quick work on this
> regression.
> 
> Robin, do you by chance have a Fixes tag which I can add?

For the sake of justifying this as "fix" rather than "cleanup", you may 
as well use the flush queue commit cited in the patch log - I maintain 
there's nothing technically wrong with that commit itself, but it is the 
point at which the underlying issue becomes worth fixing due to how they 
interact ;)

Cheers,
Robin.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2021-06-04 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 13:48 [PATCH] iommu/amd: Tidy up DMA ops init Robin Murphy
2021-06-03 13:48 ` Robin Murphy
2021-06-04 15:26 ` Joerg Roedel
2021-06-04 15:26   ` Joerg Roedel
2021-06-04 17:35   ` Robin Murphy [this message]
2021-06-04 17:35     ` Robin Murphy
2021-06-07 12:55     ` Joerg Roedel
2021-06-07 12:55       ` Joerg Roedel

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=781da5b3-4856-9a76-d803-51800dec6033@arm.com \
    --to=robin.murphy@arm.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joamaki@gmail.com \
    --cc=joro@8bytes.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 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.