public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Roel Van Nyen <roel.vannyen@gmail.com>
Cc: Belisko Marek <marek.belisko@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	acho@novell.com, error27@gmail.com
Subject: Re: [PATCH 2/2] Staging: keucr: Remove BOOLEAN type from driver.
Date: Wed, 2 Mar 2011 16:35:44 -0500	[thread overview]
Message-ID: <20110302213544.GA32685@suse.de> (raw)
In-Reply-To: <20110302211813.GA1579@roel-laptop>

On Wed, Mar 02, 2011 at 10:18:13PM +0100, Roel Van Nyen wrote:
> On Wed, Mar 02, 2011 at 10:12:15PM +0100, Belisko Marek wrote:
> > On Wed, Mar 2, 2011 at 10:04 PM, Roel Van Nyen <roel.vannyen@gmail.com> wrote:
> > > Remove BOOLEAN type, replacing it with bool and removing some that were not in use.
> > >
> > > Signed-off-by: Roel Van Nyen <roel.vannyen@gmail.com>
> > > ---
> > >  drivers/staging/keucr/common.h   |    2 --
> > >  drivers/staging/keucr/smil.h     |    4 ++--
> > >  drivers/staging/keucr/smilmain.c |    4 ++--
> > >  drivers/staging/keucr/usb.h      |    4 +---
> > >  4 files changed, 5 insertions(+), 9 deletions(-)
> > >
> > > diff --git a/drivers/staging/keucr/common.h b/drivers/staging/keucr/common.h
> > > index 07aabf4..5dda691 100644
> > > --- a/drivers/staging/keucr/common.h
> > > +++ b/drivers/staging/keucr/common.h
> > > @@ -1,8 +1,6 @@
> > >  #ifndef COMMON_INCD
> > >  #define COMMON_INCD
> > >
> > > -typedef u8 BOOLEAN;
> > > -
> > >  #define swapWORD(w)    ((((unsigned short)(w) << 8) & 0xff00) |        \
> > >                         (((unsigned short)(w) >> 8) & 0x00ff))
> > >  #define swapDWORD(dw)  ((((unsigned long)(dw) << 24) & 0xff000000) |   \
> > > diff --git a/drivers/staging/keucr/smil.h b/drivers/staging/keucr/smil.h
> > > index c108545..a3addff 100644
> > > --- a/drivers/staging/keucr/smil.h
> > > +++ b/drivers/staging/keucr/smil.h
> > > @@ -223,11 +223,11 @@ int         Media_D_OneSectWriteNext    (struct us_data *,u8 *);
> > >  int         Media_D_OneSectWriteFlush   (struct us_data *);
> > >
> > >  /******************************************/
> > > -void        SM_EnableLED                (struct us_data *,BOOLEAN);
> > > +void        SM_EnableLED                (struct us_data *, bool enabled);
> > >  void        Led_D_TernOn                (void);
> > >  void        Led_D_TernOff               (void);
> > >
> > > -int         Media_D_EraseAllRedtData    (u32 Index, BOOLEAN CheckBlock);
> > > +int         Media_D_EraseAllRedtData    (u32 Index);
> > Shouldn't there be something like:
> > int         Media_D_EraseAllRedtData    (u32 Index, bool CheckBlock); ???
> no, since the variable was not used in the first place.

That's fine, but don't do that in this patch.

Remember, do only one thing per patch, don't bury code changes in a
"remove typedefs" patch, that's not allowed at all.

sorry,

greg k-h

      reply	other threads:[~2011-03-02 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 21:04 [PATCH 2/2] Staging: keucr: Remove BOOLEAN type from driver Roel Van Nyen
2011-03-02 21:12 ` Belisko Marek
2011-03-02 21:18   ` Roel Van Nyen
2011-03-02 21:35     ` Greg KH [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=20110302213544.GA32685@suse.de \
    --to=gregkh@suse.de \
    --cc=acho@novell.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=error27@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.belisko@gmail.com \
    --cc=roel.vannyen@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