All of lore.kernel.org
 help / color / mirror / Atom feed
From: "hch@lst.de" <hch@lst.de>
To: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
Cc: "hch@lst.de" <hch@lst.de>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
	"linux-m68k@lists.linux-m68k.org"
	<linux-m68k@lists.linux-m68k.org>,
	"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>,
	"openrisc@lists.librecores.org" <openrisc@lists.librecores.org>,
	"ashutosh.dixit@intel.com" <ashutosh.dixit@intel.com>,
	"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
	"linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>,
	"monstr@monstr.eu" <monstr@monstr.eu>,
	"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>
Subject: Re: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 13:21:49 +0100	[thread overview]
Message-ID: <20181214122149.GA7309@lst.de> (raw)
In-Reply-To: <1544789518.3270.34.camel@synopsys.com>

On Fri, Dec 14, 2018 at 12:12:00PM +0000, Eugeniy Paltsev wrote:
> Hi Christoph,
> 
> do you have any public git repository with all your dma changes?

Most of the tree show up in my misc.git repo for testing.

This series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-alloc-always-zero

There current version of the DMA_ATTR_NON_CONSISTENT series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-noncoherent-allocator.2


> I want to test them for ARC.

Thanks a lot!

WARNING: multiple messages have this Message-ID (diff)
From: "hch@lst.de" <hch@lst.de>
To: Eugeniy Paltsev
	<eugeniy.paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
Cc: "linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org"
	<linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org>,
	"monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org"
	<monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>,
	"linux-c6x-dev-jPsnJVOj+W6hPH1hqNUYSQ@public.gmane.org"
	<linux-c6x-dev-jPsnJVOj+W6hPH1hqNUYSQ@public.gmane.org>,
	"linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-m68k-cunTk1MwBs8S/qaLPR03pWD2FQJk+8+b@public.gmane.org"
	<linux-m68k-cunTk1MwBs8S/qaLPR03pWD2FQJk+8+b@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"ashutosh.dixit-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<ashutosh.dixit-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	"openrisc-cunTk1MwBs9a3B2Vnqf2dGD2FQJk+8+b@public.gmane.org"
	<openrisc-cunTk1MwBs9a3B2Vnqf2dGD2FQJk+8+b@public.gmane.org>,
	"linux-alpha-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-alpha-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"hch-jcswGhMUV9g@public.gmane.org"
	<hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 12:21:49 +0000	[thread overview]
Message-ID: <20181214122149.GA7309@lst.de> (raw)
In-Reply-To: <1544789518.3270.34.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>

On Fri, Dec 14, 2018 at 12:12:00PM +0000, Eugeniy Paltsev wrote:
> Hi Christoph,
> 
> do you have any public git repository with all your dma changes?

Most of the tree show up in my misc.git repo for testing.

This series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-alloc-always-zero

There current version of the DMA_ATTR_NON_CONSISTENT series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-noncoherent-allocator.2


> I want to test them for ARC.

Thanks a lot!

WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (hch@lst.de)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 13:21:49 +0100	[thread overview]
Message-ID: <20181214122149.GA7309@lst.de> (raw)
In-Reply-To: <1544789518.3270.34.camel@synopsys.com>

On Fri, Dec 14, 2018@12:12:00PM +0000, Eugeniy Paltsev wrote:
> Hi Christoph,
> 
> do you have any public git repository with all your dma changes?

Most of the tree show up in my misc.git repo for testing.

This series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-alloc-always-zero

There current version of the DMA_ATTR_NON_CONSISTENT series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-noncoherent-allocator.2


> I want to test them for ARC.

Thanks a lot!

WARNING: multiple messages have this Message-ID (diff)
From: "hch-jcswGhMUV9g@public.gmane.org" <hch-jcswGhMUV9g@public.gmane.org>
To: Eugeniy Paltsev
	<eugeniy.paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
Cc: "linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org"
	<linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org>,
	"monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org"
	<monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>,
	"linux-c6x-dev-jPsnJVOj+W6hPH1hqNUYSQ@public.gmane.org"
	<linux-c6x-dev-jPsnJVOj+W6hPH1hqNUYSQ@public.gmane.org>,
	"linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-m68k-cunTk1MwBs8S/qaLPR03pWD2FQJk+8+b@public.gmane.org"
	<linux-m68k-cunTk1MwBs8S/qaLPR03pWD2FQJk+8+b@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"ashutosh.dixit-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<ashutosh.dixit-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	"openrisc-cunTk1MwBs9a3B2Vnqf2dGD2FQJk+8+b@public.gmane.org"
	<openrisc-cunTk1MwBs9a3B2Vnqf2dGD2FQJk+8+b@public.gmane.org>,
	"linux-alpha-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-alpha-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-snps-arc-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"hch-jcswGhMUV9g@public.gmane.org"
	<hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 13:21:49 +0100	[thread overview]
Message-ID: <20181214122149.GA7309@lst.de> (raw)
In-Reply-To: <1544789518.3270.34.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>

On Fri, Dec 14, 2018 at 12:12:00PM +0000, Eugeniy Paltsev wrote:
> Hi Christoph,
> 
> do you have any public git repository with all your dma changes?

Most of the tree show up in my misc.git repo for testing.

This series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-alloc-always-zero

There current version of the DMA_ATTR_NON_CONSISTENT series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-noncoherent-allocator.2


> I want to test them for ARC.

Thanks a lot!

WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_*
Date: Fri, 14 Dec 2018 13:21:49 +0100	[thread overview]
Message-ID: <20181214122149.GA7309@lst.de> (raw)
In-Reply-To: <1544789518.3270.34.camel@synopsys.com>

On Fri, Dec 14, 2018 at 12:12:00PM +0000, Eugeniy Paltsev wrote:
> Hi Christoph,
> 
> do you have any public git repository with all your dma changes?

Most of the tree show up in my misc.git repo for testing.

This series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-alloc-always-zero

There current version of the DMA_ATTR_NON_CONSISTENT series is here:

http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-noncoherent-allocator.2


> I want to test them for ARC.

Thanks a lot!

  reply	other threads:[~2018-12-14 12:22 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  8:25 ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14  8:25 ` [OpenRISC] " Christoph Hellwig
2018-12-14  8:25 ` Christoph Hellwig
2018-12-14  8:25 ` Christoph Hellwig
2018-12-14  8:25 ` Christoph Hellwig
2018-12-14  8:25 ` [PATCH 1/2] dma-mapping: zero memory returned from dma_alloc_* Christoph Hellwig
2018-12-14  8:25   ` [OpenRISC] " Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  9:54   ` Geert Uytterhoeven
2018-12-14  9:54     ` [OpenRISC] " Geert Uytterhoeven
2018-12-14  9:54     ` Geert Uytterhoeven
2018-12-14  9:54     ` Geert Uytterhoeven
2018-12-14  9:54     ` Geert Uytterhoeven
2018-12-14  9:55     ` Geert Uytterhoeven
2018-12-14  9:55       ` [OpenRISC] " Geert Uytterhoeven
2018-12-14  9:55       ` Geert Uytterhoeven
2018-12-14  9:55       ` Geert Uytterhoeven
2018-12-14  9:55       ` Geert Uytterhoeven
2018-12-14 11:47     ` Christoph Hellwig
2018-12-14 11:47       ` [OpenRISC] " Christoph Hellwig
2018-12-14 11:47       ` Christoph Hellwig
2018-12-14 11:47       ` Christoph Hellwig
2018-12-14 11:47       ` Christoph Hellwig
2018-12-14 12:36       ` Geert Uytterhoeven
2018-12-14 12:36         ` [OpenRISC] " Geert Uytterhoeven
2018-12-14 12:36         ` Geert Uytterhoeven
2018-12-14 12:36         ` Geert Uytterhoeven
2018-12-14 14:14       ` Greg Ungerer
2018-12-14 14:14         ` [OpenRISC] " Greg Ungerer
2018-12-14 14:14         ` Greg Ungerer
2018-12-14 14:14         ` Greg Ungerer
2018-12-14 14:14         ` Greg Ungerer
2018-12-14 14:14         ` Greg Ungerer
2018-12-17 11:59         ` Christoph Hellwig
2018-12-17 11:59           ` [OpenRISC] " Christoph Hellwig
2018-12-17 11:59           ` Christoph Hellwig
2018-12-17 11:59           ` Christoph Hellwig
2019-01-11  6:09           ` Greg Ungerer
2018-12-14 12:12   ` Eugeniy Paltsev
2018-12-14 12:12     ` [OpenRISC] " Eugeniy Paltsev
2018-12-14 12:12     ` Eugeniy Paltsev
2018-12-14 12:12     ` Eugeniy Paltsev
2018-12-14 12:12     ` Eugeniy Paltsev
2018-12-14 12:21     ` hch [this message]
2018-12-14 12:21       ` [OpenRISC] " hch
2018-12-14 12:21       ` hch-jcswGhMUV9g
2018-12-14 12:21       ` hch
2018-12-14 12:21       ` hch
2018-12-14 18:10   ` Sam Ravnborg
2018-12-14 18:10     ` [OpenRISC] " Sam Ravnborg
2018-12-14 18:10     ` Sam Ravnborg
2018-12-14 18:10     ` Sam Ravnborg
2018-12-14 18:35     ` Christoph Hellwig
2018-12-14 18:35       ` [OpenRISC] " Christoph Hellwig
2018-12-14 18:35       ` Christoph Hellwig
2018-12-14 18:35       ` Christoph Hellwig
2018-12-14  8:25 ` [PATCH 2/2] dma-mapping: deprecate dma_zalloc_coherent Christoph Hellwig
2018-12-14  8:25   ` [OpenRISC] " Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14  8:25   ` Christoph Hellwig
2018-12-14 13:33 ` ensure dma_alloc_coherent always returns zeroed memory Christoph Hellwig
2018-12-14 13:33   ` [OpenRISC] " Christoph Hellwig
2018-12-14 13:33   ` Christoph Hellwig
2018-12-14 13:33   ` Christoph Hellwig
2018-12-19 16:59 ` Christoph Hellwig
2018-12-19 16:59   ` [OpenRISC] " Christoph Hellwig
2018-12-19 16:59   ` Christoph Hellwig
2018-12-19 16:59   ` Christoph Hellwig
2018-12-20 14:32   ` Eugeniy Paltsev
2018-12-20 14:32     ` Eugeniy Paltsev
2018-12-20 14:32     ` Eugeniy Paltsev
2018-12-20 14:32     ` Eugeniy Paltsev
2018-12-20 14:34     ` hch
2018-12-20 14:34       ` [OpenRISC] " hch
2018-12-20 14:34       ` hch
2018-12-20 14:34       ` hch
2018-12-20 14:34       ` hch
2018-12-20 14:39       ` Eugeniy Paltsev
2018-12-20 14:39         ` Eugeniy Paltsev
2018-12-20 14:39         ` Eugeniy Paltsev
2018-12-20 14:39         ` Eugeniy Paltsev
2018-12-20 14:46         ` hch
2018-12-20 14:46           ` [OpenRISC] " hch
2018-12-20 14:46           ` hch
2018-12-20 14:46           ` hch
2018-12-20 14:46           ` hch
2018-12-20 17:37           ` hch
2018-12-20 17:37             ` [OpenRISC] " hch
2018-12-20 17:37             ` hch
2018-12-20 17:37             ` hch
2018-12-20 17:37             ` hch

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=20181214122149.GA7309@lst.de \
    --to=hch@lst.de \
    --cc=ashutosh.dixit@intel.com \
    --cc=eugeniy.paltsev@synopsys.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=monstr@monstr.eu \
    --cc=openrisc@lists.librecores.org \
    --cc=sparclinux@vger.kernel.org \
    /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.