From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] iommu: move pgsize_bitmap from struct iommu_ops to struct iommu_domain
Date: Fri, 6 Mar 2015 12:34:53 +0000 [thread overview]
Message-ID: <20150306123453.GK22377@arm.com> (raw)
In-Reply-To: <1973968.aLfySGl5av@avalon>
On Fri, Mar 06, 2015 at 11:57:58AM +0000, Laurent Pinchart wrote:
> On Friday 06 March 2015 11:34:47 Will Deacon wrote:
> > @@ -108,8 +109,6 @@ enum iommu_attr {
> > * @domain_get_attr: Query domain attributes
> > * @domain_set_attr: Change domain attributes
> > * @of_xlate: add OF master IDs to iommu grouping
> > - * @pgsize_bitmap: bitmap of supported page sizes
> > - * @priv: per-instance data private to the iommu driver
> > */
> > struct iommu_ops {
> > bool (*capable)(enum iommu_cap);
> > @@ -144,9 +143,6 @@ struct iommu_ops {
> > #ifdef CONFIG_OF_IOMMU
> > int (*of_xlate)(struct device *dev, struct of_phandle_args *args);
> > #endif
> > -
> > - unsigned long pgsize_bitmap;
> > - void *priv;
>
> The commit message doesn't mention the removal of the priv field.
Yup, that's sloppy. I'll move it into a separate patch.
Will
next prev parent reply other threads:[~2015-03-06 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 11:34 [PATCH 0/2] Kill off pgsize_bitmap field from struct iommu_ops Will Deacon
2015-03-06 11:34 ` [PATCH 1/2] iommu: move pgsize_bitmap from struct iommu_ops to struct iommu_domain Will Deacon
2015-03-06 11:56 ` Laurent Pinchart
2015-03-06 11:59 ` Will Deacon
2015-03-06 11:57 ` Laurent Pinchart
2015-03-06 12:34 ` Will Deacon [this message]
2015-03-06 12:24 ` Marek Szyprowski
2015-03-11 8:38 ` Thierry Reding
2015-03-06 11:34 ` [PATCH 2/2] iommu: of: enforce const-ness of struct iommu_ops Will Deacon
2015-03-11 8:43 ` Thierry Reding
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=20150306123453.GK22377@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).