Re: [PATCH char-misc-next v2 04/22] iommu: Allow iova to be used without requiring IOMMU_SUPPORT

["gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org" <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>]

On Tue, Oct 06, 2015 at 06:12:40AM +0100, gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org wrote:
> On Mon, Oct 05, 2015 at 10:38:43AM -0700, Sudeep Dutt wrote:
> > 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > > > 
> > > > iova is a library which can be built without IOMMU_SUPPORT
> > > > 
> > > > Signed-off-by: Sudeep Dutt <sudeep.dutt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > > 
> > > 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.
> 
> I can handle merge issues, that's trivial.  Reverting the patch
> shoulnd't really be needed, right?  Let me see what happens when I merge
> to see if your patch is necessary...

Ok, I don't think it is needed, the merge was pretty trivial.

Can you test out my char-misc-testing branch right now to see if it's
all ok with the merge?  If so, I'll move it all over to the "real" place
for it to start showing up in linux-next, i.e. my char-misc-next branch.

thanks,

greg k-h