[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK=WgbY+YN6aj4+RUdPz068+H+vtnEx0_SbKuKc++S4AHRS_hw@mail.gmail.com>
Date: Sun, 2 Oct 2011 20:48:41 +0200
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Grant Likely <grant.likely@...retlab.ca>
Cc: linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Hiroshi DOYU <Hiroshi.DOYU@...ia.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Joerg Roedel <Joerg.Roedel@....com>,
iommu@...ts.linux-foundation.org, Arnd Bergmann <arnd@...db.de>,
linux-kernel@...r.kernel.org, Cousson Benoit <b-cousson@...com>,
Kevin Hilman <khilman@...com>,
Tony Lindgren <tony@...mide.com>,
Russell King <linux@....linux.org.uk>
Subject: Re: [RFC 1/5] ARM: dev_archdata: add private iommu extension
On Tue, Sep 27, 2011 at 4:30 AM, Grant Likely <grant.likely@...retlab.ca> wrote:
> Blech. Oh well. Not much point in doing something different if x86
> uses a void*.
x86 probably does this because two different implementations needs to
plug their private data there: intel-iommu plugs there a 'struct
device_domain_info *' and amd_iommu uses it with a 'struct
iommu_dev_data *'.
On ARM we'd eventually end up with even a bigger variety, and I guess
that even if we'd use a type-safe member here, it would itself end up
having 'void *'.
If it looks reasonable to you, can I please have your Ack ?
Russell, can you please take a look too and ack/nack ?
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists