public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm:fix:cleanup: Volatile keyword removal
Date: Mon, 20 Feb 2012 11:39:11 +0100	[thread overview]
Message-ID: <20120220113911.34bb6d61@lmajewski.digital.local> (raw)
In-Reply-To: <4F3F893B.2010006@aribaud.net>

On Sat, 18 Feb 2012 12:19:23 +0100
Albert ARIBAUD <albert.u.boot@aribaud.net> wrote:

> Hi Lukasz,
> 
> Le 18/10/2011 16:25, Lukasz Majewski a ?crit :
> > Volatile keyword removal from
> > ./arch/arm/include/asm/bitops.h
> >
> > Signed-off-by: Lukasz Majewski<l.majewski@samsung.com>
> > Signed-off-by: Kyungmin Park<kyungmin.park@samsung.com>
> > ---
> >   arch/arm/include/asm/bitops.h |    6 +++---
> >   1 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm/include/asm/bitops.h
> > b/arch/arm/include/asm/bitops.h index 879e20e..b00ae30 100644
> > --- a/arch/arm/include/asm/bitops.h
> > +++ b/arch/arm/include/asm/bitops.h
> > @@ -25,11 +25,11 @@
> >   /*
> >    * Function prototypes to keep gcc -Wall happy.
> >    */
> > -extern void set_bit(int nr, volatile void * addr);
> > +extern void set_bit(int nr, void *addr);
> >
> > -extern void clear_bit(int nr, volatile void * addr);
> > +extern void clear_bit(int nr, void *addr);
> >
> > -extern void change_bit(int nr, volatile void * addr);
> > +extern void change_bit(int nr, void *addr);
> >
> >   static inline void __change_bit(int nr, volatile void *addr)
> >   {
> 
> Going through backlogged patches adelegated to me, I found this one.
> I'm fine with it, however I notice there is absolutely no call to
> set_bit, change_bit or clear_bit in the whole ARM subtree... What is
> the point of removing only the volatile qualifier vs removing the
> function definitions?
> 
> Amicalement,

Hi Albert,

This patch was a supplement (to quiet compiler warnings) to the USB
gadget infrastructure.

But as we know, usb:gadget hasn't been added to the u-boot mainline.

However, I'm working on this, so I predict, that in the (near) future I
would need those changes to suppress compiler warnings :-).

For now, the commit can be discarded, I will resubmit it if needed.

-- 
Best regards,

Lukasz Majewski

Samsung Poland R&D Center
Platform Group

      reply	other threads:[~2012-02-20 10:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 14:25 [U-Boot] [PATCH] arm:fix:cleanup: Volatile keyword removal Lukasz Majewski
2012-02-18 11:19 ` Albert ARIBAUD
2012-02-20 10:39   ` Lukasz Majewski [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=20120220113911.34bb6d61@lmajewski.digital.local \
    --to=l.majewski@samsung.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