From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: linux-next: runtime warning after merge of the dma-mapping tree
Date: Thu, 1 Aug 2024 15:40:57 +0200 [thread overview]
Message-ID: <20240801134057.GA2245@lst.de> (raw)
In-Reply-To: <20240801151455.01f08778@canb.auug.org.au>
Ok, I guess this is what Robin was referring to.
A midlayer like SCSI really shouldn't directly call dma layer
functions without knowing that the underlying bus is DMA capable.
I'll see what I can do about it, and in the meantime drop this patch
and the companion from the dma-mapping tree.
prev parent reply other threads:[~2024-08-01 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 5:14 linux-next: runtime warning after merge of the dma-mapping tree Stephen Rothwell
2024-08-01 13:40 ` 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=20240801134057.GA2245@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=sfr@canb.auug.org.au \
/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).