From: Christoph Hellwig <hch@lst.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Christoph Hellwig <hch@lst.de>,
rubini@gnudd.com, hch@infradead.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 2/2] x86/PCI: sta2x11: use default DMA address translation
Date: Thu, 14 Nov 2019 08:29:47 +0100 [thread overview]
Message-ID: <20191114072947.GA26546@lst.de> (raw)
In-Reply-To: <20191113185420.GC1647@zn.tnic>
On Wed, Nov 13, 2019 at 07:54:20PM +0100, Borislav Petkov wrote:
> Ok, I have only 2/2 in my mbox so in the future, when sending a whole
> set, make sure you Cc everybody on all the patches so that people can
> see the whole thing.
>
> Then, I went and read back all the discussion about this cleanup and
> how it is hard to test it because it is not in PCs but in automotive
> installations...
>
> Long story, short, I like patches with negative diffstats :) so I could
> take it through tip unless Christoph has different plans for this.
I've already queued this up in the dma-mapping tree.
prev parent reply other threads:[~2019-11-14 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 15:06 [PATCH v3 0/2] x86: Get rid of custom DMA functions Nicolas Saenz Julienne
2019-11-07 15:06 ` Nicolas Saenz Julienne
2019-11-07 15:06 ` [PATCH v3 1/2] dma-direct: check for overflows on 32 bit DMA addresses Nicolas Saenz Julienne
2019-11-07 15:06 ` Nicolas Saenz Julienne
2019-11-07 15:06 ` [PATCH v3 2/2] x86/PCI: sta2x11: use default DMA address translation Nicolas Saenz Julienne
2019-11-13 18:54 ` Borislav Petkov
2019-11-14 7:29 ` Christoph Hellwig [this message]
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=20191114072947.GA26546@lst.de \
--to=hch@lst.de \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nsaenzjulienne@suse.de \
--cc=rubini@gnudd.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.