From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: dts: socfpga: fix DTC unit name warnings
Date: Tue, 19 Apr 2016 07:01:13 +0200 [thread overview]
Message-ID: <5715BB99.6020906@denx.de> (raw)
In-Reply-To: <57151EC8.8020800@denx.de>
Hello Marek,
Am 18.04.2016 um 19:52 schrieb Marek Vasut:
> On 04/18/2016 05:46 PM, Tom Rini wrote:
>> On Mon, Apr 18, 2016 at 05:37:02PM +0200, Marek Vasut wrote:
>>> On 04/18/2016 05:31 PM, Tom Rini wrote:
>>>> On Fri, Apr 15, 2016 at 12:41:02PM +0200, Heiko Schocher wrote:
>>>>
>>>>> Fix following DTC warnings for all socfpga boards:
>>>>
>>>> We're going to defer on this patch for now, thanks.
>>>>
>>> Can you elaborate please?
>>
>> Yes, I did in another of the threads here (aside, I wish this was done a
>> series and there was a 0/N, but, oh well). We import these from the
>> kernel, as this isn't a U-Boot change, we're the wrong place to start
>> making these changes by and large. In some quick googling around, the
>> various SoC trees are updating to fix these problems and we'll pull them
>> in whenever our relevant custodian is happy. Or when someone can say
>> "resync with $hash from the kernel" and get them Acked-by or whatever.
>>
> You will want to backport this patch, it's in linux-next too:
>
> http://www.spinics.net/lists/linux-kbuild/msg12538.html
Yes ... we ignore warnings ... maybe an agreement ...
I can prepare a patch for this, but I prefer to add this build flag
for each arch, so we can at least remove it for each arch, when all
warnings are fixed in linux and we did a sync with linux ...
Would this be OK?
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2016-04-19 5:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 10:41 [U-Boot] [PATCH] arm: dts: socfpga: fix DTC unit name warnings Heiko Schocher
2016-04-15 14:18 ` Marek Vasut
2016-04-18 4:55 ` Heiko Schocher
2016-04-18 10:36 ` Marek Vasut
2016-04-18 11:20 ` Heiko Schocher
2016-04-18 11:22 ` Marek Vasut
2016-04-17 21:55 ` Pavel Machek
2016-04-18 6:07 ` Heiko Schocher
2016-04-18 10:00 ` Pavel Machek
2016-04-18 10:35 ` Marek Vasut
2016-04-18 11:06 ` Heiko Schocher
2016-04-18 15:31 ` Tom Rini
2016-04-18 15:37 ` Marek Vasut
2016-04-18 15:46 ` Tom Rini
2016-04-18 17:52 ` Marek Vasut
2016-04-19 5:01 ` Heiko Schocher [this message]
2016-04-19 10:38 ` Marek Vasut
2016-04-19 4:47 ` Heiko Schocher
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=5715BB99.6020906@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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