linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Claire Chang <tientzu@chromium.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Will Deacon <will@kernel.org>,
	pasic@linux.ibm.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] (swiotlb) stable/for-linus-5.15
Date: Fri, 3 Sep 2021 10:37:10 -0700	[thread overview]
Message-ID: <CAHk-=wiGs=YDah3mBfi5A0Vh7OMeLfk3yOw219nvRAeghLmHGg@mail.gmail.com> (raw)
In-Reply-To: <ab606dd7-87a7-25cd-8f0e-841638cc40e3@arm.com>

On Fri, Sep 3, 2021 at 6:51 AM Robin Murphy <robin.murphy@arm.com> wrote:
>
> > "essentially"? "shouldn't be expected"? I'm not getting a lot of warm
> > and fuzzies from that. I'd like to have something a bit more concrete.
>
> As above, upstream Kconfigs do prevent any possible overlap at the
> moment (with "swiotlb: use depends on for DMA_RESTRICTED_POOL" fixing
> the bug which inadvertently made SWIOTLB user-selectable).

Ok. I've done the merge, I do hope that this code can be clarified at
some point in the future.

             Linus

  reply	other threads:[~2021-09-03 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 21:08 [GIT PULL] (swiotlb) stable/for-linus-5.15 Konrad Rzeszutek Wilk
2021-09-02 18:54 ` Linus Torvalds
2021-09-02 21:55   ` Robin Murphy
2021-09-03  0:42     ` Linus Torvalds
2021-09-03  5:09       ` Christoph Hellwig
2021-09-03 13:51       ` Robin Murphy
2021-09-03 17:37         ` Linus Torvalds [this message]
2021-09-03 18:45 ` pr-tracker-bot

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='CAHk-=wiGs=YDah3mBfi5A0Vh7OMeLfk3yOw219nvRAeghLmHGg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=pasic@linux.ibm.com \
    --cc=robin.murphy@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=tientzu@chromium.org \
    --cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).