From: Joerg Roedel <jroedel@suse.de>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu: Don't attach deferred device in iommu_group_do_dma_attach
Date: Thu, 4 Jun 2020 11:16:19 +0200 [thread overview]
Message-ID: <20200604091619.GO6857@suse.de> (raw)
In-Reply-To: <20200604073142.74701-1-jsnitsel@redhat.com>
Hi Jerry,
On Thu, Jun 04, 2020 at 12:31:42AM -0700, Jerry Snitselaar wrote:
> Attaching a deferred device should be delayed until dma api is called.
>
> Cc: iommu@lists.linux-foundation.org
> Suggested-by: Joerg Roedel <jroedel@suse.de>
> Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
> ---
> If you already have thrown a patch together, then ignore this. Also
> feel free to swap out the signed-off-by with your's since
> this is more your patch than mine. You can put a reviewed-by
> and tested-by instead for me.
Yeah, I already have a patch, just not sent out yet. I updated it with
your tags and will send it out shortly.
Regards,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <jroedel@suse.de>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: Re: [PATCH] iommu: Don't attach deferred device in iommu_group_do_dma_attach
Date: Thu, 4 Jun 2020 11:16:19 +0200 [thread overview]
Message-ID: <20200604091619.GO6857@suse.de> (raw)
In-Reply-To: <20200604073142.74701-1-jsnitsel@redhat.com>
Hi Jerry,
On Thu, Jun 04, 2020 at 12:31:42AM -0700, Jerry Snitselaar wrote:
> Attaching a deferred device should be delayed until dma api is called.
>
> Cc: iommu@lists.linux-foundation.org
> Suggested-by: Joerg Roedel <jroedel@suse.de>
> Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
> ---
> If you already have thrown a patch together, then ignore this. Also
> feel free to swap out the signed-off-by with your's since
> this is more your patch than mine. You can put a reviewed-by
> and tested-by instead for me.
Yeah, I already have a patch, just not sent out yet. I updated it with
your tags and will send it out shortly.
Regards,
Joerg
next prev parent reply other threads:[~2020-06-04 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 7:31 [PATCH] iommu: Don't attach deferred device in iommu_group_do_dma_attach Jerry Snitselaar
2020-06-04 7:31 ` Jerry Snitselaar
2020-06-04 9:16 ` Joerg Roedel [this message]
2020-06-04 9:16 ` 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=20200604091619.GO6857@suse.de \
--to=jroedel@suse.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jsnitsel@redhat.com \
--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.