lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 6 Oct 2015 06:20:29 +0100
From:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To:	Sudeep Dutt <sudeep.dutt@...el.com>
Cc:	"Woodhouse, David" <david.woodhouse@...el.com>,
	"Dixit, Ashutosh" <ashutosh.dixit@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.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 Tue, Oct 06, 2015 at 06:12:40AM +0100, gregkh@...uxfoundation.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@...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.
> 
> 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
--
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