From: Christoph Hellwig <hch@lst.de>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>, Jens Axboe <axboe@kernel.dk>,
Joerg Roedel <joro@8bytes.org>, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Paul Burton <paulburton@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
x86@kernel.org, phil@raspberrypi.org, linux-acpi@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>, James Hogan <jhogan@kernel.org>,
Len Brown <lenb@kernel.org>,
devicetree@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-mips@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
iommu@lists.linux-foundation.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] dma-mapping: treat dev->bus_dma_mask as a DMA limit
Date: Tue, 19 Nov 2019 18:00:06 +0100 [thread overview]
Message-ID: <20191119170006.GA19569@lst.de> (raw)
In-Reply-To: <dd074ef5c23ba56598e92be19e8e25ae31b75f93.camel@suse.de>
On Tue, Nov 19, 2019 at 01:57:43PM +0100, Nicolas Saenz Julienne wrote:
> Hi Rob & Christoph,
> do you mind if I append v2 of this into my upcoming v3 RPi4 PCIe support
> series, I didn't do it initially as I thought this was going to be a
> contentious patch. But as it turned out better than expected, I think it
> should go into the PCIe series. In the end it's the first explicit user of the
> bus DMA limit.
>
> Here's v2 in case you don't know what I'm talking about:
> https://www.spinics.net/lists/arm-kernel/msg768459.html
In principle I wouldn't mind, but I think this is going to conflict
quite badly with other changes in the dma-mapping tree (including
yours). So I think we'll need a shared tree or I'll need to pull
in the whole series through the dma-mapping tree if there are not
other conflicts and the other maintainers are fine with it.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-mips@vger.kernel.org, linux-ide@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
Hanjun Guo <guohanjun@huawei.com>,
Frank Rowand <frowand.list@gmail.com>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Paul Burton <paulburton@kernel.org>,
Joerg Roedel <joro@8bytes.org>,
x86@kernel.org, phil@raspberrypi.org, linux-acpi@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
linux-pci@vger.kernel.org, James Hogan <jhogan@kernel.org>,
Len Brown <lenb@kernel.org>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
Jens Axboe <axboe@kernel.dk>,
linuxppc-dev@lists.ozlabs.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
iommu@lists.linux-foundation.org,
Sudeep Holla <sudeep.holla@arm.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] dma-mapping: treat dev->bus_dma_mask as a DMA limit
Date: Tue, 19 Nov 2019 18:00:06 +0100 [thread overview]
Message-ID: <20191119170006.GA19569@lst.de> (raw)
In-Reply-To: <dd074ef5c23ba56598e92be19e8e25ae31b75f93.camel@suse.de>
On Tue, Nov 19, 2019 at 01:57:43PM +0100, Nicolas Saenz Julienne wrote:
> Hi Rob & Christoph,
> do you mind if I append v2 of this into my upcoming v3 RPi4 PCIe support
> series, I didn't do it initially as I thought this was going to be a
> contentious patch. But as it turned out better than expected, I think it
> should go into the PCIe series. In the end it's the first explicit user of the
> bus DMA limit.
>
> Here's v2 in case you don't know what I'm talking about:
> https://www.spinics.net/lists/arm-kernel/msg768459.html
In principle I wouldn't mind, but I think this is going to conflict
quite badly with other changes in the dma-mapping tree (including
yours). So I think we'll need a shared tree or I'll need to pull
in the whole series through the dma-mapping tree if there are not
other conflicts and the other maintainers are fine with it.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-mips@vger.kernel.org, linux-ide@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
Hanjun Guo <guohanjun@huawei.com>,
Frank Rowand <frowand.list@gmail.com>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Paul Burton <paulburton@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Joerg Roedel <joro@8bytes.org>,
x86@kernel.org, phil@raspberrypi.org, linux-acpi@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
linux-pci@vger.kernel.org, James Hogan <jhogan@kernel.org>,
Len Brown <lenb@kernel.org>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
Jens Axboe <axboe@kernel.dk>,
linuxppc-dev@lists.ozlabs.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
iommu@lists.linux-foundation.org,
Sudeep Holla <sudeep.holla@arm.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] dma-mapping: treat dev->bus_dma_mask as a DMA limit
Date: Tue, 19 Nov 2019 18:00:06 +0100 [thread overview]
Message-ID: <20191119170006.GA19569@lst.de> (raw)
In-Reply-To: <dd074ef5c23ba56598e92be19e8e25ae31b75f93.camel@suse.de>
On Tue, Nov 19, 2019 at 01:57:43PM +0100, Nicolas Saenz Julienne wrote:
> Hi Rob & Christoph,
> do you mind if I append v2 of this into my upcoming v3 RPi4 PCIe support
> series, I didn't do it initially as I thought this was going to be a
> contentious patch. But as it turned out better than expected, I think it
> should go into the PCIe series. In the end it's the first explicit user of the
> bus DMA limit.
>
> Here's v2 in case you don't know what I'm talking about:
> https://www.spinics.net/lists/arm-kernel/msg768459.html
In principle I wouldn't mind, but I think this is going to conflict
quite badly with other changes in the dma-mapping tree (including
yours). So I think we'll need a shared tree or I'll need to pull
in the whole series through the dma-mapping tree if there are not
other conflicts and the other maintainers are fine with it.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-19 17:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 16:13 [PATCH] dma-mapping: treat dev->bus_dma_mask as a DMA limit Nicolas Saenz Julienne
2019-11-13 16:13 ` Nicolas Saenz Julienne
2019-11-13 16:13 ` Nicolas Saenz Julienne
2019-11-13 16:13 ` Nicolas Saenz Julienne
2019-11-13 20:34 ` Robin Murphy
2019-11-13 20:34 ` Robin Murphy
2019-11-13 20:34 ` Robin Murphy
2019-11-13 20:34 ` Robin Murphy
2019-11-13 20:41 ` Florian Fainelli
2019-11-13 20:41 ` Florian Fainelli
2019-11-13 20:41 ` Florian Fainelli
2019-11-13 20:41 ` Florian Fainelli
2019-11-13 21:24 ` Robin Murphy
2019-11-13 21:24 ` Robin Murphy
2019-11-13 21:24 ` Robin Murphy
2019-11-13 21:24 ` Robin Murphy
2019-11-14 9:47 ` Nicolas Saenz Julienne
2019-11-14 9:47 ` Nicolas Saenz Julienne
2019-11-14 9:47 ` Nicolas Saenz Julienne
2019-11-14 9:47 ` Nicolas Saenz Julienne
2019-11-14 7:34 ` Christoph Hellwig
2019-11-14 7:34 ` Christoph Hellwig
2019-11-14 7:34 ` Christoph Hellwig
2019-11-14 7:34 ` Christoph Hellwig
2019-11-19 12:57 ` Nicolas Saenz Julienne
2019-11-19 12:57 ` Nicolas Saenz Julienne
2019-11-19 12:57 ` Nicolas Saenz Julienne
2019-11-19 17:00 ` Christoph Hellwig [this message]
2019-11-19 17:00 ` Christoph Hellwig
2019-11-19 17:00 ` Christoph Hellwig
2019-11-19 17:17 ` Robin Murphy
2019-11-19 17:17 ` Robin Murphy
2019-11-19 17:17 ` Robin Murphy
2019-11-21 7:31 ` Christoph Hellwig
2019-11-21 7:31 ` Christoph Hellwig
2019-11-21 7:31 ` Christoph Hellwig
2019-11-21 7:31 ` Christoph Hellwig
2019-11-21 9:18 ` Nicolas Saenz Julienne
2019-11-21 9:18 ` Nicolas Saenz Julienne
2019-11-21 9:18 ` Nicolas Saenz Julienne
2019-11-21 9:18 ` Nicolas Saenz Julienne
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=20191119170006.GA19569@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=guohanjun@huawei.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jhogan@kernel.org \
--cc=joro@8bytes.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=luto@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=nsaenzjulienne@suse.de \
--cc=paulburton@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=phil@raspberrypi.org \
--cc=ralf@linux-mips.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=x86@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.