From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Hounschell <markh@compro.net>
Cc: Christoph Hellwig <hch@lst.de>,
Robin Murphy <robin.murphy@arm.com>,
Linux-kernel <linux-kernel@vger.kernel.org>,
dmaengine@vger.kernel.org
Subject: Re: [BUG] dma-mapping: remove CONFIG_DMA_REMAP
Date: Tue, 21 Jun 2022 16:51:42 +0200 [thread overview]
Message-ID: <YrHa/vwLds+HG6jl@kroah.com> (raw)
In-Reply-To: <c32d2da1-9122-66bd-12fc-916be79b33fd@compro.net>
On Tue, Jun 21, 2022 at 09:43:18AM -0400, Mark Hounschell wrote:
> Revert that commit and all works like normal. This commit breaks user land.
Seems like it only breaks an out-of-tree driver, and for obvious
reasons, there's nothing we can do about that, sorry. You are on your
own here. Please work with your company to get your driver merged to
the tree and then we will be glad to help out with these types of
issues.
thanks,
greg k-h
prev parent reply other threads:[~2022-06-21 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:43 [BUG] dma-mapping: remove CONFIG_DMA_REMAP Mark Hounschell
2022-06-21 13:48 ` Christoph Hellwig
2022-06-21 14:06 ` Mark Hounschell
2022-06-21 14:19 ` Christoph Hellwig
2022-06-21 14:31 ` Mark Hounschell
2022-06-21 14:51 ` Greg KH [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=YrHa/vwLds+HG6jl@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmaengine@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=robin.murphy@arm.com \
/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