All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	Christoph Hellwig <hch@lst.de>,
	dri-devel@lists.freedesktop.org,
	laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH] dma-mapping: remove dma_{alloc,free,mmap}_writecombine
Date: Tue, 30 Jul 2019 12:20:50 +0200	[thread overview]
Message-ID: <20190730102050.GA1663@lst.de> (raw)
In-Reply-To: <5f73f400-eff2-6c7b-887d-c768642d8df1@ti.com>

On Tue, Jul 30, 2019 at 10:50:32AM +0300, Tomi Valkeinen wrote:
> On 30/07/2019 09:18, Christoph Hellwig wrote:
>> We can already use DMA_ATTR_WRITE_COMBINE or the _wc prefixed version,
>> so remove the third way of doing things.
>>
>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>> ---
>>   drivers/gpu/drm/omapdrm/dss/dispc.c | 11 +++++------
>>   include/linux/dma-mapping.h         |  9 ---------
>>   2 files changed, 5 insertions(+), 15 deletions(-)
>
> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>
> Which tree should this be applied to?

I'd like to add it to the dma-mapping tree if possible.
_______________________________________________
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: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Christoph Hellwig <hch@lst.de>,
	laurent.pinchart@ideasonboard.com,
	dri-devel@lists.freedesktop.org,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-mapping: remove dma_{alloc,free,mmap}_writecombine
Date: Tue, 30 Jul 2019 12:20:50 +0200	[thread overview]
Message-ID: <20190730102050.GA1663@lst.de> (raw)
In-Reply-To: <5f73f400-eff2-6c7b-887d-c768642d8df1@ti.com>

On Tue, Jul 30, 2019 at 10:50:32AM +0300, Tomi Valkeinen wrote:
> On 30/07/2019 09:18, Christoph Hellwig wrote:
>> We can already use DMA_ATTR_WRITE_COMBINE or the _wc prefixed version,
>> so remove the third way of doing things.
>>
>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>> ---
>>   drivers/gpu/drm/omapdrm/dss/dispc.c | 11 +++++------
>>   include/linux/dma-mapping.h         |  9 ---------
>>   2 files changed, 5 insertions(+), 15 deletions(-)
>
> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>
> Which tree should this be applied to?

I'd like to add it to the dma-mapping tree if possible.

  reply	other threads:[~2019-07-30 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30  6:18 [PATCH] dma-mapping: remove dma_{alloc,free,mmap}_writecombine Christoph Hellwig
2019-07-30  6:18 ` Christoph Hellwig
2019-07-30  6:18 ` Christoph Hellwig
2019-07-30  7:50 ` Tomi Valkeinen via iommu
2019-07-30  7:50   ` Tomi Valkeinen
2019-07-30  7:50   ` Tomi Valkeinen
2019-07-30 10:20   ` Christoph Hellwig [this message]
2019-07-30 10:20     ` Christoph Hellwig
2019-07-30 11:23     ` Tomi Valkeinen via iommu
2019-07-30 11:23       ` Tomi Valkeinen
2019-07-30 11:23       ` Tomi Valkeinen
2019-07-30 13:50 ` Laurent Pinchart
2019-07-30 13:50   ` Laurent Pinchart
2019-08-29 14:54   ` Christoph Hellwig
2019-08-29 14:54     ` Christoph Hellwig

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=20190730102050.GA1663@lst.de \
    --to=hch@lst.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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.