public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 2/2] Freescale eLBC FCM NAND driver
Date: Tue, 25 Mar 2008 20:33:44 +0100	[thread overview]
Message-ID: <200803252033.44495.sr@denx.de> (raw)
In-Reply-To: <47E930F8.8010005@freescale.com>

On Tuesday 25 March 2008, Scott Wood wrote:
> >> +static void fsl_elbc_select_chip(struct mtd_info *mtd, int chip)
> >> +{
> >> +	/* The hardware does not seem to support multiple
> >> +	 * chips per bank.
> >> +	 */
> >
> > please use this comment style
>
> Do we really need such trivial style differences with the Linux driver,
> which will only serve as an annoyance when keeping the two in sync, not
> to mention wasting vertical space with no readability benefit because
> there's pretty much always a (mostly) blank line above the comment?

This preferred comment style *should* be used. But I would not object to your 
(and others) multi-line comment style either. It's being used in Linux 
frequently and as you already mentioned saves one line. Especially when 
moving Linux drivers to U-Boot, we should allow this coding style for better 
maintenance.

Just my 2 cents.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

      reply	other threads:[~2008-03-25 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 17:53 [U-Boot-Users] [PATCH 2/2] Freescale eLBC FCM NAND driver Scott Wood
2008-03-25 16:49 ` Jean-Christophe PLAGNIOL-VILLARD
2008-03-25 17:06   ` Scott Wood
2008-03-25 19:33     ` Stefan Roese [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=200803252033.44495.sr@denx.de \
    --to=sr@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