public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: 'Christoph Hellwig' <hch@lst•de>
To: David Laight <David.Laight@ACULAB•COM>
Cc: 'Christoph Hellwig' <hch@lst•de>,
	"iommu@lists•linux-foundation.org"
	<iommu@lists•linux-foundation.org>,
	Chris Zankel <chris@zankel•net>, Michal Simek <monstr@monstr•eu>,
	"linux-ia64@vger•kernel.org" <linux-ia64@vger•kernel.org>,
	"linux-mips@linux-mips•org" <linux-mips@linux-mips•org>,
	"linux-sh@vger•kernel.org" <linux-sh@vger•kernel.org>,
	"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
	"linux-xtensa@linux-xtensa•org" <linux-xtensa@linux-xtensa•org>,
	"x86@kernel•org" <x86@kernel•org>,
	"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
	David Howells <dhowells@redhat•com>,
	Max Filippov <jcmvbkbc@gmail•com>,
	Guan Xuetao <gxt@mprc•pku.edu.cn>,
	Robin Murphy <robin.murphy@arm•com>,
	Marek Szyprowski <m.szyprowski@samsung•com>
Subject: Re: [PATCH 04/11] ia64: make dma_cache_sync a no-op
Date: Wed, 4 Oct 2017 11:06:31 +0200	[thread overview]
Message-ID: <20171004090631.GA23669@lst.de> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DD0089626@AcuExch.aculab.com>

On Wed, Oct 04, 2017 at 08:59:24AM +0000, David Laight wrote:
> Are you sure about this one?

Yes.  And if you are not you haven't read either of the cover letter,
the DMA-API documentation, or the reply from Thomas to your mail
yesterday.

  reply	other threads:[~2017-10-04  9:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 10:43 refactor dma_cache_sync V2 Christoph Hellwig
2017-10-03 10:43 ` [PATCH 01/11] floppy: consolidate the dummy fd_cacheflush definition Christoph Hellwig
2017-10-03 10:43 ` [PATCH 02/11] x86: make dma_cache_sync a no-op Christoph Hellwig
2017-10-03 16:02   ` David Laight
2017-10-03 20:27     ` Thomas Gleixner
2017-10-03 10:43 ` [PATCH 03/11] frv: " Christoph Hellwig
2017-10-03 10:43 ` [PATCH 04/11] ia64: " Christoph Hellwig
2017-10-04  8:59   ` David Laight
2017-10-04  9:06     ` 'Christoph Hellwig' [this message]
2017-10-03 10:43 ` [PATCH 05/11] microblaze: " Christoph Hellwig
2017-10-03 10:43 ` [PATCH 06/11] mn10300: " Christoph Hellwig
2017-10-03 10:43 ` [PATCH 07/11] powerpc: " Christoph Hellwig
2017-10-03 11:24   ` Christophe LEROY
2017-10-03 11:43     ` Robin Murphy
2017-10-03 11:43     ` Christoph Hellwig
2017-10-04  8:29       ` Christophe LEROY
2017-10-03 10:43 ` [PATCH 08/11] unicore32: " Christoph Hellwig
2017-10-03 10:43 ` [PATCH 09/11] xtensa: " Christoph Hellwig
2017-10-03 10:43 ` [PATCH 10/11] sh: " Christoph Hellwig
2017-10-03 10:43 ` [PATCH 11/11] dma-mapping: turn dma_cache_sync into a dma_map_ops method Christoph Hellwig
2017-10-03 11:49 ` refactor dma_cache_sync V2 Robin Murphy
2017-10-16 12:44   ` Christoph Hellwig
2017-10-19 15:02     ` 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=20171004090631.GA23669@lst.de \
    --to=hch@lst$(echo .)de \
    --cc=David.Laight@ACULAB$(echo .)COM \
    --cc=chris@zankel$(echo .)net \
    --cc=dhowells@redhat$(echo .)com \
    --cc=gxt@mprc$(echo .)pku.edu.cn \
    --cc=iommu@lists$(echo .)linux-foundation.org \
    --cc=jcmvbkbc@gmail$(echo .)com \
    --cc=linux-ia64@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mips@linux-mips$(echo .)org \
    --cc=linux-sh@vger$(echo .)kernel.org \
    --cc=linux-xtensa@linux-xtensa$(echo .)org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=m.szyprowski@samsung$(echo .)com \
    --cc=monstr@monstr$(echo .)eu \
    --cc=robin.murphy@arm$(echo .)com \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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