From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] imx: mx6 move TARGET_xx Kconfig option to mx6 specific Kconfig file
Date: Fri, 07 Aug 2015 09:33:02 +0200 [thread overview]
Message-ID: <55C45F2E.5050503@denx.de> (raw)
In-Reply-To: <55C45BFA.5020703@web.de>
Hi Peng, Soeren,
On 07/08/2015 09:19, Soeren Moch wrote:
> Peng,
>
> Sorry for being unclear here.
>
> In your patch you add several options in arch/arm/cpu/armv7/mx6/Kconfig
> under "MX6 board select". Some of these options are named "Support
> <boardname>" (e.g. "Support udoo"), while others are simply called
> "<boardname>" (e.g. "Bachmann OT1200").
>
> I would prefer the simple "<boardname>" naming style for all options and
> remove the word "Support" from all description strings. But this is only
> my personal opinion and a minor cosmetic change.
Checking in other architecture, I see there is no rule about this. Even
in the same Kconfig (AT91), there is a mix with and without "Support".
Both are ok - decide yourself.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2015-08-07 7:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 5:43 [U-Boot] [PATCH] imx: mx6 move TARGET_xx Kconfig option to mx6 specific Kconfig file Peng Fan
2015-08-06 9:18 ` Stefano Babic
2015-08-06 9:34 ` Soeren Moch
2015-08-07 1:17 ` Peng Fan
2015-08-07 7:19 ` Soeren Moch
2015-08-07 7:33 ` Stefano Babic [this message]
2015-08-07 10:02 ` Marek Vasut
2015-08-07 13:47 ` Masahiro Yamada
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=55C45F2E.5050503@denx.de \
--to=sbabic@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