From: Chris Metcalf <cmetcalf@tilera.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tile: Add underscores to defintions
Date: Thu, 10 Jul 2014 14:19:59 -0400 [thread overview]
Message-ID: <53BED94F.9020407@tilera.com> (raw)
In-Reply-To: <1404534728-7345-1-git-send-email-xerofoify@gmail.com>
On 7/5/2014 12:32 AM, Nicholas Krause wrote:
> In file drv_xgbe_impl.h I fixed the definitions for Size Small,
> Size Large, Size Jumbo to have underscores before and after to
> follow kernel coding style for internel defentions.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> arch/tile/include/hv/drv_xgbe_impl.h | 15 +++------------
I don't think there is a kernel coding style for internal definitions.
It's true that double-underscores mean "more raw" in many places, like
for things like set_bit() vs __set_bit(), but that's not really
applicable here. These files are not exported outside of the kernel
in any case so we don't need any special treatment for them to mark them
as "internal definitions".
The comment in any case certainly is silly. It dates back to Jan 2007
in our internal version control system. The tilepro hv headers in
question are largely frozen at this point in our internal "upstream"
repository where we take these headers from, so it doesn't seem worth
the effort to try to improve the comments there, nor worth adding skew
between those headers and the community headers.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2014-07-10 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 4:32 [PATCH] tile: Add underscores to defintions Nicholas Krause
2014-07-10 18:19 ` Chris Metcalf [this message]
2014-07-10 18:50 ` Nick Krause
2014-07-10 19:15 ` Chris Metcalf
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=53BED94F.9020407@tilera.com \
--to=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xerofoify@gmail.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