dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: kevin.tian@intel.com, nicolinc@nvidia.com, leonro@nvidia.com,
	leon@kernel.org, dri-devel@lists.freedesktop.org,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] dma-buf: remove pci-p2pdma include from dma-buf.h
Date: Mon, 21 Sep 2026 09:25:46 -0300	[thread overview]
Message-ID: <20260921122546.GA1487657@nvidia.com> (raw)
In-Reply-To: <20260921094452.679455-1-christian.koenig@amd.com>

On Mon, Sep 21, 2026 at 11:44:52AM +0200, Christian König wrote:
> That is unecessary here and creates an unwanted dependency to the PCI
> subsystem. Move that into dma-buf-mapping.h instead.
> 
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
>  include/linux/dma-buf-mapping.h | 1 +
>  include/linux/dma-buf.h         | 1 -
>  2 files changed, 1 insertion(+), 1 deletion(-)

> diff --git a/include/linux/dma-buf-mapping.h b/include/linux/dma-buf-mapping.h
> index 09bde3f748e4..fb5e52260700 100644
> --- a/include/linux/dma-buf-mapping.h
> +++ b/include/linux/dma-buf-mapping.h
> @@ -6,6 +6,7 @@
>  #ifndef __DMA_BUF_MAPPING_H__
>  #define __DMA_BUF_MAPPING_H__
>  #include <linux/dma-buf.h>
> +#include <linux/pci-p2pdma.h>
>  
>  struct sg_table *dma_buf_phys_vec_to_sgt(struct dma_buf_attachment *attach,
>  					 struct p2pdma_provider *provider,

Let's just use a forward declaration instead of the whole header:

struct p2pdma_provider;

Jason

      parent reply	other threads:[~2026-09-21 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  9:44 [PATCH] dma-buf: remove pci-p2pdma include from dma-buf.h Christian König
2026-09-21  9:58 ` sashiko-bot
2026-09-21 12:25 ` Jason Gunthorpe [this message]

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=20260921122546.GA1487657@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=christian.koenig@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kevin.tian@intel.com \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=nicolinc@nvidia.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