All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	christian.koenig@amd.com, kevin.tian@intel.com,
	jacob.jun.pan@linux.intel.com, ashok.raj@intel.com,
	baolu.lu@linux.intel.com, zhangfei.gao@foxmail.com
Subject: Re: [PATCH v3 1/1] iommu: Bind process address spaces to devices
Date: Thu, 11 Apr 2019 17:28:03 +0200	[thread overview]
Message-ID: <20190411152803.GB29810@8bytes.org> (raw)
In-Reply-To: <20190410151516.47754-2-jean-philippe.brucker@arm.com>

On Wed, Apr 10, 2019 at 04:15:16PM +0100, Jean-Philippe Brucker wrote:
>  drivers/iommu/iommu.c | 104 ++++++++++++++++++++++++++++++++++++++++++
>  include/linux/iommu.h |  70 ++++++++++++++++++++++++++++
>  2 files changed, 174 insertions(+)

Applied to the api-features branch for now, thanks Jean-Philippe!

'for now' because I have a question below.

> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> index ed6738c358ca..87fe1cddd817 100644
> --- a/include/linux/iommu.h
> +++ b/include/linux/iommu.h
> @@ -51,10 +51,13 @@ struct device;
>  struct iommu_domain;
>  struct notifier_block;
>  struct iommu_fault_event;
> +struct iommu_sva;

The iommu_fault_event doesn't yet exist in my tree, is this patch based
on something else I need besided Lu Baolus work? I got quite some
conflicts while applying the patch because of this.

> + * @sva_set_ops: Set ops for a SVA handle

I also removed this line.

Regards,

	Joerg

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: kevin.tian@intel.com, ashok.raj@intel.com,
	zhangfei.gao@foxmail.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org, christian.koenig@amd.com
Subject: Re: [PATCH v3 1/1] iommu: Bind process address spaces to devices
Date: Thu, 11 Apr 2019 17:28:03 +0200	[thread overview]
Message-ID: <20190411152803.GB29810@8bytes.org> (raw)
Message-ID: <20190411152803.Sa2yZvLkkgnrqwgTA6LVKYJjZyJsYvAq-ggUt2WhZac@z> (raw)
In-Reply-To: <20190410151516.47754-2-jean-philippe.brucker@arm.com>

On Wed, Apr 10, 2019 at 04:15:16PM +0100, Jean-Philippe Brucker wrote:
>  drivers/iommu/iommu.c | 104 ++++++++++++++++++++++++++++++++++++++++++
>  include/linux/iommu.h |  70 ++++++++++++++++++++++++++++
>  2 files changed, 174 insertions(+)

Applied to the api-features branch for now, thanks Jean-Philippe!

'for now' because I have a question below.

> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> index ed6738c358ca..87fe1cddd817 100644
> --- a/include/linux/iommu.h
> +++ b/include/linux/iommu.h
> @@ -51,10 +51,13 @@ struct device;
>  struct iommu_domain;
>  struct notifier_block;
>  struct iommu_fault_event;
> +struct iommu_sva;

The iommu_fault_event doesn't yet exist in my tree, is this patch based
on something else I need besided Lu Baolus work? I got quite some
conflicts while applying the patch because of this.

> + * @sva_set_ops: Set ops for a SVA handle

I also removed this line.

Regards,

	Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-04-11 15:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 15:15 [PATCH v3 0/1] IOMMU SVA device driver interface Jean-Philippe Brucker
2019-04-10 15:15 ` Jean-Philippe Brucker
2019-04-10 15:15 ` [PATCH v3 1/1] iommu: Bind process address spaces to devices Jean-Philippe Brucker
2019-04-10 15:15   ` Jean-Philippe Brucker
2019-04-11 15:28   ` Joerg Roedel [this message]
2019-04-11 15:28     ` Joerg Roedel
     [not found]     ` <20190411152803.GB29810-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2019-04-12 12:23       ` Jean-Philippe Brucker
2019-04-12 12:23         ` Jean-Philippe Brucker
2019-04-12 12:23         ` Jean-Philippe Brucker
2019-04-12 14:59         ` Joerg Roedel
2019-04-12 14:59           ` Joerg Roedel
     [not found]           ` <20190412145954.GD29810-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2019-04-12 16:05             ` Jean-Philippe Brucker
2019-04-12 16:05               ` Jean-Philippe Brucker
2019-04-12 16:05               ` Jean-Philippe Brucker

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=20190411152803.GB29810@8bytes.org \
    --to=joro@8bytes.org \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=christian.koenig@amd.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jean-philippe.brucker@arm.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhangfei.gao@foxmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.