From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Will Deacon <will@kernel.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
iommu@lists.linux-foundation.org,
Claire Chang <tientzu@chromium.org>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v2 0/4] Fix restricted DMA vs swiotlb_exit()
Date: Fri, 23 Jul 2021 20:29:16 -0400 [thread overview]
Message-ID: <YPte3K+4PPjGAQt/@fedora> (raw)
In-Reply-To: <20210720133826.9075-1-will@kernel.org>
On Tue, Jul 20, 2021 at 02:38:22PM +0100, Will Deacon wrote:
> Hi again, folks,
>
> This is version two of the patch series I posted yesterday:
>
> https://lore.kernel.org/r/20210719123054.6844-1-will@kernel.org
>
> The only changes since v1 are:
>
> * Squash patches 2 and 3, amending the commit message accordingly
> * Add Reviewed-by and Tested-by tags from Christoph and Claire (thanks!)
>
> I'd usually leave it a bit longer between postings, but since this fixes
> issues with patches in -next I thought I'd spin a new version immediately.
Thank you!
I put them in devel/for-linus-5.15 and linux-next.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Will Deacon <will@kernel.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Claire Chang <tientzu@chromium.org>,
Christoph Hellwig <hch@lst.de>,
Robin Murphy <robin.murphy@arm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v2 0/4] Fix restricted DMA vs swiotlb_exit()
Date: Fri, 23 Jul 2021 20:29:16 -0400 [thread overview]
Message-ID: <YPte3K+4PPjGAQt/@fedora> (raw)
In-Reply-To: <20210720133826.9075-1-will@kernel.org>
On Tue, Jul 20, 2021 at 02:38:22PM +0100, Will Deacon wrote:
> Hi again, folks,
>
> This is version two of the patch series I posted yesterday:
>
> https://lore.kernel.org/r/20210719123054.6844-1-will@kernel.org
>
> The only changes since v1 are:
>
> * Squash patches 2 and 3, amending the commit message accordingly
> * Add Reviewed-by and Tested-by tags from Christoph and Claire (thanks!)
>
> I'd usually leave it a bit longer between postings, but since this fixes
> issues with patches in -next I thought I'd spin a new version immediately.
Thank you!
I put them in devel/for-linus-5.15 and linux-next.
next prev parent reply other threads:[~2021-07-24 0:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 13:38 [PATCH v2 0/4] Fix restricted DMA vs swiotlb_exit() Will Deacon
2021-07-20 13:38 ` Will Deacon
2021-07-20 13:38 ` [PATCH v2 1/4] of: Return success from of_dma_set_restricted_buffer() when !OF_ADDRESS Will Deacon
2021-07-20 13:38 ` Will Deacon
2021-07-20 13:38 ` [PATCH v2 2/4] swiotlb: Convert io_default_tlb_mem to static allocation Will Deacon
2021-07-20 13:38 ` Will Deacon
2021-07-20 13:38 ` [PATCH v2 3/4] swiotlb: Emit diagnostic in swiotlb_exit() Will Deacon
2021-07-20 13:38 ` Will Deacon
2021-07-20 13:38 ` [PATCH v2 4/4] swiotlb: Free tbl memory " Will Deacon
2021-07-20 13:38 ` Will Deacon
2021-07-31 18:26 ` Guenter Roeck
2021-07-31 18:26 ` Guenter Roeck
2021-08-01 2:29 ` Konrad Rzeszutek Wilk
2021-08-01 2:29 ` Konrad Rzeszutek Wilk
2021-08-01 4:26 ` Guenter Roeck
2021-08-01 4:26 ` Guenter Roeck
2021-07-22 19:22 ` [PATCH v2 0/4] Fix restricted DMA vs swiotlb_exit() Christian Borntraeger
2021-07-22 19:22 ` Christian Borntraeger
2021-07-23 1:12 ` Halil Pasic
2021-07-23 1:12 ` Halil Pasic
2021-07-23 5:51 ` Christian Borntraeger
2021-07-23 5:51 ` Christian Borntraeger
2021-07-23 6:14 ` Christian Borntraeger
2021-07-23 6:14 ` Christian Borntraeger
2021-07-23 8:47 ` Halil Pasic
2021-07-23 8:47 ` Halil Pasic
2021-07-23 8:50 ` Christian Borntraeger
2021-07-23 8:50 ` Christian Borntraeger
2021-07-23 14:01 ` Konrad Rzeszutek Wilk
2021-07-23 14:01 ` Konrad Rzeszutek Wilk
2021-07-23 17:53 ` Christian Borntraeger
2021-07-23 17:53 ` Christian Borntraeger
2021-07-23 22:18 ` Halil Pasic
2021-07-23 22:18 ` Halil Pasic
2021-07-24 0:29 ` Konrad Rzeszutek Wilk [this message]
2021-07-24 0:29 ` Konrad Rzeszutek Wilk
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=YPte3K+4PPjGAQt/@fedora \
--to=konrad@darnok.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nathan@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tientzu@chromium.org \
--cc=will@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.