All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 3/5] dma-mapping: make support for dma ops optional
Date: Mon, 20 Jul 2020 08:20:24 +0200	[thread overview]
Message-ID: <20200720062024.GA10878@lst.de> (raw)
In-Reply-To: <20200718171714.GA237687@roeck-us.net>

On Sat, Jul 18, 2020 at 10:17:14AM -0700, Guenter Roeck wrote:
> On Wed, Jul 08, 2020 at 05:24:47PM +0200, Christoph Hellwig wrote:
> > Avoid the overhead of the dma ops support for tiny builds that only
> > use the direct mapping.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> For ppc:pmac32_defconfig and other configurations, this patch results in:

Fixed and force pushed.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 3/5] dma-mapping: make support for dma ops optional
Date: Mon, 20 Jul 2020 08:20:24 +0200	[thread overview]
Message-ID: <20200720062024.GA10878@lst.de> (raw)
In-Reply-To: <20200718171714.GA237687@roeck-us.net>

On Sat, Jul 18, 2020 at 10:17:14AM -0700, Guenter Roeck wrote:
> On Wed, Jul 08, 2020 at 05:24:47PM +0200, Christoph Hellwig wrote:
> > Avoid the overhead of the dma ops support for tiny builds that only
> > use the direct mapping.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> For ppc:pmac32_defconfig and other configurations, this patch results in:

Fixed and force pushed.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Christoph Hellwig <hch@lst.de>,
	iommu@lists.linux-foundation.org,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Robin Murphy <robin.murphy@arm.com>,
	linux-kernel@vger.kernel.org,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 3/5] dma-mapping: make support for dma ops optional
Date: Mon, 20 Jul 2020 08:20:24 +0200	[thread overview]
Message-ID: <20200720062024.GA10878@lst.de> (raw)
In-Reply-To: <20200718171714.GA237687@roeck-us.net>

On Sat, Jul 18, 2020 at 10:17:14AM -0700, Guenter Roeck wrote:
> On Wed, Jul 08, 2020 at 05:24:47PM +0200, Christoph Hellwig wrote:
> > Avoid the overhead of the dma ops support for tiny builds that only
> > use the direct mapping.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> For ppc:pmac32_defconfig and other configurations, this patch results in:

Fixed and force pushed.

  reply	other threads:[~2020-07-20  6:20 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 15:24 generic DMA bypass flag v4 Christoph Hellwig
2020-07-08 15:24 ` Christoph Hellwig
2020-07-08 15:24 ` Christoph Hellwig
2020-07-08 15:24 ` [PATCH 1/5] dma-mapping: move the remaining DMA API calls out of line Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-08 15:24 ` [PATCH 2/5] dma-mapping: inline the fast path dma-direct calls Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-08 15:24 ` [PATCH 3/5] dma-mapping: make support for dma ops optional Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-09 18:10   ` kernel test robot
2020-07-18 17:17   ` Guenter Roeck
2020-07-18 17:17     ` Guenter Roeck
2020-07-18 17:17     ` Guenter Roeck
2020-07-20  6:20     ` Christoph Hellwig [this message]
2020-07-20  6:20       ` Christoph Hellwig
2020-07-20  6:20       ` Christoph Hellwig
2020-07-08 15:24 ` [PATCH 4/5] dma-mapping: add a dma_ops_bypass flag to struct device Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-13  4:59   ` Alexey Kardashevskiy
2020-07-13  4:59     ` Alexey Kardashevskiy
2020-07-13  4:59     ` Alexey Kardashevskiy
2020-07-14  7:07     ` Christoph Hellwig
2020-07-14  7:07       ` Christoph Hellwig
2020-07-14  7:07       ` Christoph Hellwig
2020-07-14  7:12       ` Alexey Kardashevskiy
2020-07-14  7:12         ` Alexey Kardashevskiy
2020-07-14  7:12         ` Alexey Kardashevskiy
2020-07-08 15:24 ` [PATCH 5/5] powerpc: use the generic dma_ops_bypass mode Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-07-08 15:24   ` Christoph Hellwig
2020-08-30  9:04   ` Cédric Le Goater
2020-08-30  9:04     ` Cédric Le Goater
2020-08-30  9:04     ` Cédric Le Goater
2020-08-31  6:40     ` Christoph Hellwig
2020-08-31  6:40       ` Christoph Hellwig
2020-08-31  6:40       ` Christoph Hellwig
2020-08-31  7:19       ` Cédric Le Goater
2020-08-31  7:19         ` Cédric Le Goater
2020-08-31  7:19         ` Cédric Le Goater
2020-09-05 15:45       ` Alexey Kardashevskiy
2020-09-05 15:45         ` Alexey Kardashevskiy
2020-09-05 15:45         ` Alexey Kardashevskiy
2020-07-10 13:26 ` generic DMA bypass flag v4 Jesper Dangaard Brouer
2020-07-10 13:26   ` Jesper Dangaard Brouer
2020-07-10 13:26   ` Jesper Dangaard Brouer

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=20200720062024.GA10878@lst.de \
    --to=hch@lst.de \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=robin.murphy@arm.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.