linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Dutt <sudeep.dutt@intel.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Sudeep Dutt <sudeep.dutt@intel.com>,
	"Woodhouse, David" <david.woodhouse@intel.com>,
	"Dixit, Ashutosh" <ashutosh.dixit@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Rao, Nikhil" <nikhil.rao@intel.com>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>
Subject: Re: [PATCH char-misc-next v2 04/22] iommu: Allow iova to be used without requiring IOMMU_SUPPORT
Date: Mon, 05 Oct 2015 22:23:38 -0700	[thread overview]
Message-ID: <1444109018.93285.176.camel@localhost> (raw)
In-Reply-To: <20151006052029.GA7959@kroah.com>

On Tue, 2015-10-06 at 06:20 +0100, gregkh@linuxfoundation.org wrote:
> On Tue, Oct 06, 2015 at 06:12:40AM +0100, gregkh@linuxfoundation.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@intel.com>
> > > > > 
> > > > > iova is a library which can be built without IOMMU_SUPPORT
> > > > > 
> > > > > Signed-off-by: Sudeep Dutt <sudeep.dutt@intel.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.
> 

Hi Greg,

I think it is best to revert this patch as it is incorrect. The iommu
folder gets compiled only if IOMMU_SUPPORT is enabled so IOMMU_IOVA
should indeed be included only when IOMMU_SUPPORT is enabled.

Sincere apologies for the mess here but I believe it will all get fixed
up if you accept the revert of 353649e5da I sent across earlier today.

Thanks,
Sudeep Dutt


  reply	other threads:[~2015-10-06  5:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  1:06 [PATCH char-misc-next v2 00/22] misc: mic: Enable COSM and remaining SCIF functionality Ashutosh Dixit
2015-09-30  1:07 ` [PATCH char-misc-next v2 01/22] iommu: iova: Move iova cache management to the iova library Ashutosh Dixit
2015-09-30  1:07 ` [PATCH char-misc-next v2 02/22] iommu: iova: Export symbols Ashutosh Dixit
2015-09-30  1:08 ` [PATCH char-misc-next v2 03/22] iommu: Make the iova library a module Ashutosh Dixit
2015-09-30  1:09 ` [PATCH char-misc-next v2 04/22] iommu: Allow iova to be used without requiring IOMMU_SUPPORT Ashutosh Dixit
2015-10-05 10:50   ` Woodhouse, David
2015-10-05 17:38     ` Sudeep Dutt
2015-10-06  5:12       ` gregkh
2015-10-06  5:20         ` gregkh
2015-10-06  5:23           ` Sudeep Dutt [this message]
2015-10-06  7:56             ` gregkh
2015-10-06  8:05               ` Sudeep Dutt
2015-10-06  8:33                 ` gregkh
2015-10-06 12:04                   ` Sudeep Dutt
2015-09-30  1:09 ` [PATCH char-misc-next v2 05/22] dma: Add support to program MIC x100 status descriptiors Ashutosh Dixit
2015-09-30  1:10 ` [PATCH char-misc-next v2 06/22] misc: mic: SCIF poll Ashutosh Dixit
2015-09-30  1:11 ` [PATCH char-misc-next v2 07/22] misc: mic: Add support for kernel mode SCIF clients Ashutosh Dixit
2015-09-30  1:12 ` [PATCH char-misc-next v2 08/22] misc: mic: MIC COSM bus Ashutosh Dixit
2015-09-30  1:12 ` [PATCH char-misc-next v2 09/22] misc: mic: Coprocessor State Management (COSM) driver Ashutosh Dixit
2015-09-30  1:12 ` [PATCH char-misc-next v2 10/22] misc: mic: COSM SCIF server Ashutosh Dixit
2015-09-30  1:13 ` [PATCH char-misc-next v2 11/22] misc: mic: COSM client driver Ashutosh Dixit
2015-09-30  1:13 ` [PATCH char-misc-next v2 12/22] misc: mic: Remove COSM functionality from the MIC host driver Ashutosh Dixit
2015-09-30  1:13 ` [PATCH char-misc-next v2 13/22] misc: mic: Remove COSM functionality from the MIC card driver Ashutosh Dixit
2015-09-30  1:14 ` [PATCH char-misc-next v2 14/22] misc: mic: Update MIC host daemon with COSM changes Ashutosh Dixit
2015-09-30  1:15 ` [PATCH char-misc-next v2 15/22] misc: mic: SCIF RMA header file and IOCTL changes Ashutosh Dixit
2015-09-30  1:15 ` [PATCH char-misc-next v2 16/22] misc: mic: SCIF RMA header file Ashutosh Dixit
2015-09-30  1:15 ` [PATCH char-misc-next v2 17/22] misc: mic: SCIF memory registration and unregistration Ashutosh Dixit
2015-09-30  1:15 ` [PATCH char-misc-next v2 18/22] misc: mic: SCIF RMA list operations Ashutosh Dixit
2015-09-30  1:15 ` [PATCH char-misc-next v2 19/22] misc: mic: SCIF remote memory map/unmap interface Ashutosh Dixit
2015-09-30  1:16 ` [PATCH char-misc-next v2 20/22] misc: mic: SCIF DMA and CPU copy interface Ashutosh Dixit
2015-09-30  1:16 ` [PATCH char-misc-next v2 21/22] misc: mic: SCIF fence Ashutosh Dixit
2015-09-30  1:16 ` [PATCH char-misc-next v2 22/22] misc: mic: SCIF RMA nodeqp and minor miscellaneous changes Ashutosh Dixit

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=1444109018.93285.176.camel@localhost \
    --to=sudeep.dutt@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=david.woodhouse@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikhil.rao@intel.com \
    --cc=sakari.ailus@linux.intel.com \
    /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).