public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Remove volatile qualifier in get_ram_size() calls
Date: Sat, 09 Jul 2011 08:34:08 +0200	[thread overview]
Message-ID: <4E17F660.1060402@aribaud.net> (raw)
In-Reply-To: <1309708533-18008-1-git-send-email-albert.u.boot@aribaud.net>

Hi Wolfgang,

Le 03/07/2011 17:55, Albert ARIBAUD a ?crit :
> Checkpatch.pl complains about the volatile qualifier in calls to
> get_ram_size(). Remove this qualifier in the prototype and in the
> calls where it is useless, and leave it only in the function body
> where it is needed.
>
> Signed-off-by: Albert ARIBAUD<albert.u.boot@aribaud.net>
> ---
> This change just prevents checkpatch from emitting spurious warnings;
> it does not affect the building process or results. It has been tested
> by comparing the build logs for jadecpu with and without the patch,
> using BUILD_NCPUS=1 to ensure both logs were ordered identically. The
> binaries were also compared (actually the .srec files) and found
> identical except for the version string.

There seems to be no comments or dissents for this patch. Can it get in? 
I can pull it into u-boot-arm, but as it is a codebase-global change I 
would prefer it to go into u-boot so that all repositories can be 
rebased on it and any issues or incompatibilities can be uncovered as 
early as possible.

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-07-09  6:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03 15:55 [U-Boot] [PATCH] Remove volatile qualifier in get_ram_size() calls Albert ARIBAUD
2011-07-09  6:34 ` Albert ARIBAUD [this message]
2011-07-17 15:13 ` Albert ARIBAUD

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=4E17F660.1060402@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --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