mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Qian Cai <cai@lca.pw>, Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Will Deacon <will@kernel.org>, Christoph Hellwig <hch@lst.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: "arm64: use asm-generic/dma-mapping.h" introduced a kbuild warning
Date: Fri, 20 Sep 2019 14:42:42 +0100	[thread overview]
Message-ID: <32e53c34-6cc5-6231-6069-3b782f5d2cf0@arm.com> (raw)
In-Reply-To: <1568985515.5576.195.camel@lca.pw>

On 20/09/2019 14:18, Qian Cai wrote:
> On Fri, 2019-09-20 at 19:24 +0900, Masahiro Yamada wrote:
>> Hi Qian,
>>
>> On Thu, Sep 19, 2019 at 10:06 PM Qian Cai <cai@lca.pw> wrote:
>>>
>>> The commit 5489c8e0cf03 ("arm64: use asm-generic/dma-mapping.h") introduced a
>>> kbuild warning,
>>>
>>> scripts/Makefile.asm-generic:25: redundant generic-y found in
>>> arch/arm64/include/asm/Kbuild: dma-mapping.h
>>>
>>>
>>
>> Which tree did you test?
> 
> It was yesterday's linux-next (next-20190918) with this config [1], but it seems
> gone in today's linux-next.

There was a conflict in dma-mapping.h between the arm64 tree and the 
dma-mapping tree (where that commit deleted it) - looks like -next must 
have just resolved it the wrong way that day.

Robin.

> [1] https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
> 
>>
>> I tried the latest Linus tree (, which contains 5489c8e0cf03),
>> but I did not see this warning.
>>
>>
>>
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

      reply	other threads:[~2019-09-20 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 13:06 Qian Cai
2019-09-20 10:24 ` Masahiro Yamada
2019-09-20 13:18   ` Qian Cai
2019-09-20 13:42     ` Robin Murphy [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=32e53c34-6cc5-6231-6069-3b782f5d2cf0@arm.com \
    --to=robin.murphy@arm.com \
    --cc=cai@lca.pw \
    --cc=hch@lst.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=sstabellini@kernel.org \
    --cc=will@kernel.org \
    --cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®