From: Stefan Agner <stefan-XLVq0VzYD2Y@public.gmane.org>
To: Jingchang Lu <jingchang.lu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org
Subject: Re: [PATCHv6 0/6] ARM: imx: Add Freescale LS1021A SoC and board support
Date: Tue, 28 Oct 2014 23:17:02 +0100 [thread overview]
Message-ID: <7bd04bef7b8e2eb701a4fe91603a0dc1@agner.ch> (raw)
In-Reply-To: <1414335419636.17637-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Am 2014-10-26 15:57, schrieb Jingchang Lu:
<snip>
>>> ---
>>> changes in v6:
>>> add dts patch description.
>>> remove '-' from QDS and TWR board dts name for consistence with u-boot.
>
>>I'm not sure it's a good idea. The most idiomatic DTS naming schema is
> just <socname>-<boardname>.dts.
> Many our PowerPC platforms doesn't have '-' between SoCs and board
> names. This becomes a project requirement when integrating in our SDK
> release, and I have renamed these board names internally, so I also
> rename them on upstream for consistence. Thanks.
Especially since this SoC has a letter in the end, its quite hard to
tell what is the SoC name and what is the board name. Hence I vote for
the hyphen too.
--
Stefan
>
> Best Regards,
> Jingchang
>
>>Shawn
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-10-28 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 10:08 [PATCHv6 0/6] ARM: imx: Add Freescale LS1021A SoC and board support Jingchang Lu
[not found] ` <1414145327-23541-1-git-send-email-jingchang.lu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-10-24 10:08 ` [PATCHv6 1/6] ARM: dts: Add SoC level device tree support for LS1021A Jingchang Lu
2014-10-24 10:08 ` [PATCHv6 2/6] ARM: dts: Add initial LS1021A QDS board dts support Jingchang Lu
2014-10-24 10:08 ` [PATCHv6 3/6] ARM: dts: Add initial LS1021A TWR " Jingchang Lu
2014-10-24 10:08 ` [PATCHv5 RESEND 4/6] dt-bindings: arm: add Freescale LS1021A SoC device tree binding Jingchang Lu
2014-10-24 10:08 ` [PATCHv5 RESEND 5/6] ARM: imx: Add initial support for Freescale LS1021A Jingchang Lu
2014-10-24 10:08 ` [PATCHv6 6/6] ARM: imx: Add Freescale LS1021A SMP support Jingchang Lu
2014-10-26 0:23 ` [PATCHv6 0/6] ARM: imx: Add Freescale LS1021A SoC and board support Shawn Guo
2014-10-26 14:57 ` Jingchang Lu
[not found] ` <1414335419636.17637-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-10-28 22:17 ` Stefan Agner [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=7bd04bef7b8e2eb701a4fe91603a0dc1@agner.ch \
--to=stefan-xlvq0vzyd2y@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jingchang.lu-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).