From: hch@lst.de (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: Warnings in arch/arm64/mm/dma-mapping.c
Date: Fri, 2 Nov 2018 19:26:49 +0100 [thread overview]
Message-ID: <20181102182649.GA11085@lst.de> (raw)
In-Reply-To: <20181102174723.GI218059@arrakis.emea.arm.com>
On Fri, Nov 02, 2018 at 05:47:24PM +0000, Catalin Marinas wrote:
> On Tue, Oct 30, 2018 at 10:13:42AM +0000, Will Deacon wrote:
> > On Tue, Oct 30, 2018 at 08:43:44AM +0100, Christoph Hellwig wrote:
> > > On Mon, Oct 29, 2018 at 04:51:47PM -0700, Florian Fainelli wrote:
> > > > I have not a chance to run a bisection yet, but I suspect this is coming
> > > > from Christoph's latest batch of DMA-API changes in ARM64 under the
> > > > merge commit befa93633193e5327e4045d1e5fa29114580fa5d ("Merge tag
> > > > 'dma-mapping-4.20-1' of git://git.infradead.org/users/hch/dma-mapping"),
> > > > here are the warnings:
> > >
> > > This should fix it:
> >
> > Tested-by: Will Deacon <will.deacon@arm.com>
> >
> > I guess Catalin can pick this up for -rc1, since there's also the kprobes
> > RO fix kicking around for arm64?
>
> I can pick it up at -rc1 as I don't have Christoph's patches in my tree
> (and don't want to base a branch on some random point in the merging
> window).
>
> Alternatively, it could go via Christoph's tree for -rc1.
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
I'll send it on tomorrow.
prev parent reply other threads:[~2018-11-02 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a771d5ce-28a2-609e-5fd7-338fadc20743@gmail.com>
2018-10-30 7:43 ` Warnings in arch/arm64/mm/dma-mapping.c Christoph Hellwig
2018-10-30 10:13 ` Will Deacon
2018-10-30 17:10 ` Florian Fainelli
2018-11-02 17:47 ` Catalin Marinas
2018-11-02 18:26 ` 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=20181102182649.GA11085@lst.de \
--to=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.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.