From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm: mx6: Change defines ENET_xxMHz to ENET_xxMHZ (no CamelCase)
Date: Mon, 15 Dec 2014 23:34:24 +0100 [thread overview]
Message-ID: <20141215223424.GA27866@amd> (raw)
In-Reply-To: <1417092403-26965-1-git-send-email-sr@denx.de>
On Thu 2014-11-27 13:46:43, Stefan Roese wrote:
> As checkpatch complaines about these camel-case defines, lets change
> them to only use upper-case characters.
Actually, it would be better to fix checkpatch. MHz is not
camelcase... Fortunately MHZ is unique, but theres real difference
between MB and Mb...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2014-12-15 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 12:46 [U-Boot] [PATCH v2] arm: mx6: Change defines ENET_xxMHz to ENET_xxMHZ (no CamelCase) Stefan Roese
2014-11-27 12:53 ` Fabio Estevam
2014-12-01 9:38 ` Stefano Babic
2014-12-15 22:34 ` Pavel Machek [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=20141215223424.GA27866@amd \
--to=pavel@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