From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: OMAP4 naming conventions
Date: Tue, 12 May 2009 07:58:45 -0700 [thread overview]
Message-ID: <87tz3qe5ay.fsf@deeprootsystems.com> (raw)
As the OMAP4 patches are coming in, there seems to be a bit of variety
in the naming of functions/macros/variables etc.
Could I propose that we just use omap4_* and OMAP4_* instead of
OMAP44XX_* or OMAP4XXXX_* etc.
I know that OMAP2 and OMAP3 have a variety of forms here too, but
those should probably be cleaned up eventually too.
With proper runtime revision detecting, IMO, we should only really
have the OMAP4 prefix, and leave the sub revision handling to runtime
code.
Thoughts?
Kevin
next reply other threads:[~2009-05-12 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 14:58 Kevin Hilman [this message]
2009-05-12 15:00 ` OMAP4 naming conventions Premi, Sanjeev
2009-05-12 15:17 ` Tony Lindgren
2009-05-12 15:18 ` Shilimkar, Santosh
2009-05-12 15:24 ` Paul Walmsley
2009-05-12 16:47 ` Kevin Hilman
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=87tz3qe5ay.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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