[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1444066723.93285.146.camel@localhost>
Date: Mon, 05 Oct 2015 10:38:43 -0700
From: Sudeep Dutt <sudeep.dutt@...el.com>
To: "Woodhouse, David" <david.woodhouse@...el.com>
Cc: Sudeep Dutt <sudeep.dutt@...el.com>,
"Dixit, Ashutosh" <ashutosh.dixit@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"Rao, Nikhil" <nikhil.rao@...el.com>,
"joro@...tes.org" <joro@...tes.org>,
"sakari.ailus@...ux.intel.com" <sakari.ailus@...ux.intel.com>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>
Subject: Re: [PATCH char-misc-next v2 04/22] iommu: Allow iova to be used
without requiring IOMMU_SUPPORT
On Mon, 2015-10-05 at 03:50 -0700, Woodhouse, David wrote:
> On Tue, 2015-09-29 at 18:09 -0700, Ashutosh Dixit wrote:
> > From: Sudeep Dutt <sudeep.dutt@...el.com>
> >
> > iova is a library which can be built without IOMMU_SUPPORT
> >
> > Signed-off-by: Sudeep Dutt <sudeep.dutt@...el.com>
>
> The first three of these patches are in 4.3-rc4 already. Apologies for
> the delay in pushing them out.
>
> This one looks sane enough too, but perhaps in that case we should move
> the code *out* of drivers/iommu/ and into lib/iova/ ?
>
Yes, moving the code into lib/iova is the correct long term solution. I
have sent Greg a patch which reverts this commit since it is no longer
required and will create a merge conflict for him unnecessarily as well
with 4.3-rc4.
Thanks,
Sudeep Dutt
--
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