public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH-OMAP3] OMAP3: Use I2C file coding style
Date: Sat, 8 Nov 2008 20:09:08 +0100	[thread overview]
Message-ID: <20081108190908.GC19090@game.jcrosoft.org> (raw)
In-Reply-To: <49107931.25e2660a.2bad.3cc1@mx.google.com>

On 17:32 Tue 04 Nov     , dirk.behme at googlemail.com wrote:
> Subject: [PATCH-OMAP3] OMAP3: Use I2C file coding style
> 
> From: Dirk Behme <dirk.behme@gmail.com>
> 
> Use file coding style for inx/outx instead of global coding style.
> 
> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
> 
> ---
> 
> Note: There was an additional review comment about this file:
> 
> -- cut --
> > +#define inb(a) __raw_readb(a)
> > +#define outb(a, v) __raw_writeb(a, v)
> >  #define inw(a) __raw_readw(a)
> >  #define outw(a,v) __raw_writew(a,v)
> 
> This 4 macro is supposed to be defined in io.h
> -- cut --
> 
> In ARM's io.h there are already inx/outx macros, but with different syntax. The correct fix for omap24xx_i2c.c will be to replace all inx/outx by readx/writex macros and remove above defines. But this can't be done on OMAP3 branch, as it would conflict with "no general coding style clean up in OMAP3 patches, only OMAP3 related changes, please". Thus, we have to do code style changes for this file at mainline once OMAP3 is merged. Until then we have to stay with consistent local style.

I desagree,

This fix is supposed to be done before appling of the OMAP3 patch set not
after.

please do not add code which need to fix just after.

NB : applied to the omap3 branch

Best Regards,
J.

  reply	other threads:[~2008-11-08 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 16:32 [U-Boot] [PATCH-OMAP3] OMAP3: Use I2C file coding style dirk.behme at googlemail.com
2008-11-08 19:09 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-11-09  7:38   ` Dirk Behme
2008-11-09 13:18     ` Jean-Christophe PLAGNIOL-VILLARD

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=20081108190908.GC19090@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --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