From: Will Deacon <will@kernel.org>
To: joro@8bytes.org, John Garry <john.garry@huawei.com>
Cc: Will Deacon <will@kernel.org>,
catalin.marinas@arm.com, 0x7f454c46@gmail.com,
linuxarm@huawei.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, kernel-team@android.com,
robin.murphy@arm.com
Subject: Re: [PATCH 0/3] IOMMU: Some IOVA code tidy-up
Date: Tue, 8 Dec 2020 15:54:30 +0000 [thread overview]
Message-ID: <160743688897.2940119.3009790405455404921.b4-ty@kernel.org> (raw)
In-Reply-To: <1607020492-189471-1-git-send-email-john.garry@huawei.com>
On Fri, 4 Dec 2020 02:34:49 +0800, John Garry wrote:
> This series contains some minor tidy-ups by deleting an unreferenced
> function and unexporting some functions, highlighted by:
> https://lore.kernel.org/linux-iommu/6e09d847-fb7f-1ec1-02bf-f0c8b315845f@huawei.com/T/#med5a019f9d3835c162c16a48f34d05cc0111b0ca
>
> John Garry (3):
> iommu: Delete split_and_remove_iova()
> iommu: Stop exporting alloc_iova_mem()
> iommu: Stop exporting free_iova_mem()
>
> [...]
Applied to arm64 (for-next/iommu/iova), thanks!
[1/3] iommu: Delete split_and_remove_iova()
https://git.kernel.org/arm64/c/2f24dfb71208
[2/3] iommu: Stop exporting alloc_iova_mem()
https://git.kernel.org/arm64/c/51b70b817b18
[3/3] iommu: Stop exporting free_iova_mem()
https://git.kernel.org/arm64/c/176cfc187c24
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-12-08 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 18:34 [PATCH 0/3] IOMMU: Some IOVA code tidy-up John Garry
2020-12-03 18:34 ` [PATCH 1/3] iommu: Delete split_and_remove_iova() John Garry
2020-12-03 18:34 ` [PATCH 2/3] iommu: Stop exporting alloc_iova_mem() John Garry
2020-12-03 18:34 ` [PATCH 3/3] iommu: Stop exporting free_iova_mem() John Garry
2020-12-08 15:54 ` Will Deacon [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=160743688897.2940119.3009790405455404921.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=john.garry@huawei.com \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=robin.murphy@arm.com \
/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).