From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
hch@lst.de, Sasha Levin <sashal@kernel.org>,
m.szyprowski@samsung.com, linux- stable <stable@vger.kernel.org>,
iommu@lists.linux-foundation.org,
open list <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
lkft-triage@lists.linaro.org
Subject: Re: dma-direct: don't check swiotlb=force in dma_direct_map_resource
Date: Tue, 7 Jan 2020 19:26:36 +0100 [thread overview]
Message-ID: <20200107182636.GA2021584@kroah.com> (raw)
In-Reply-To: <2c401e83-99d2-925f-66fe-fffe04415e1a@arm.com>
On Tue, Jan 07, 2020 at 06:18:28PM +0000, Robin Murphy wrote:
> On 07/01/2020 5:38 pm, Naresh Kamboju wrote:
> > Following build error on stable-rc 5.4.9-rc1 for arm architecture.
> >
> > dma/direct.c: In function 'dma_direct_possible':
> > dma/direct.c:329:3: error: too many arguments to function 'dma_capable'
> > dma_capable(dev, dma_addr, size, true);
> > ^~~~~~~~~~~
>
> Not sure that $SUBJECT comes into it at all, but by the look of it I guess
> "dma-direct: exclude dma_direct_map_resource from the min_low_pfn check"
> implicitly depends on 130c1ccbf553 ("dma-direct: unify the dma_capable
> definitions") too.
Ugh, good catch. I'll drop these patches, they don't look ok for stable
at this point in time.
thanks,
greg k-h
prev parent reply other threads:[~2020-01-07 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 17:38 dma-direct: don't check swiotlb=force in dma_direct_map_resource Naresh Kamboju
2020-01-07 18:18 ` Robin Murphy
2020-01-07 18:26 ` Greg Kroah-Hartman [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=20200107182636.GA2021584@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=m.szyprowski@samsung.com \
--cc=naresh.kamboju@linaro.org \
--cc=robin.murphy@arm.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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