From: Rusty Russell <rusty@rustcorp.com.au>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 12/15] module_param: make bool parameters really bool (drivers & misc)
Date: Wed, 04 Jan 2012 12:57:51 +1030 [thread overview]
Message-ID: <8762gsdwwo.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20120103124420.GA3626@mwanda>
On Tue, 3 Jan 2012 15:44:20 +0300, Dan Carpenter <dan.carpenter@oracle.com> wrote:
Non-text part: multipart/signed
> > diff --git a/drivers/video/intelfb/intelfbdrv.c b/drivers/video/intelfb/intelfbdrv.c
> > --- a/drivers/video/intelfb/intelfbdrv.c
> > +++ b/drivers/video/intelfb/intelfbdrv.c
> > @@ -230,16 +230,16 @@ MODULE_DESCRIPTION("Framebuffer driver f
> > MODULE_LICENSE("Dual BSD/GPL");
> > MODULE_DEVICE_TABLE(pci, intelfb_pci_table);
> >
> > -static int accel = 1;
> > +static bool accel = 1;
> > static int vram = 4;
> > -static int hwcursor = 0;
> > -static int mtrr = 1;
> > -static int fixed = 0;
> > -static int noinit = 0;
> > -static int noregister = 0;
> > -static int probeonly = 0;
> > -static int idonly = 0;
> > -static int bailearly = 0;
> > +static bool hwcursor = 0;
> > +static bool mtrr = 1;
> > +static bool fixed = 0;
> > +static bool noinit = 0;
> > +static bool noregister = 0;
> > +static bool probeonly = 0;
> > +static bool idonly = 0;
> > +static bool bailearly = 0;
>
> bailearly should be an int here. It's part of some ugly debug code
> where a value of 3 means bailout at point 3. Maybe we should just
> remove it instead...
Yeah, it never worked, since you could only ever set it to 0 or 1:
module_param(bailearly, bool, 0);
On Tue, 3 Jan 2012 15:58:13 +0300, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> On Thu, Dec 15, 2011 at 01:48:51PM +1030, Rusty Russell wrote:
> > diff --git a/drivers/block/paride/pcd.c b/drivers/block/paride/pcd.c
> > --- a/drivers/block/paride/pcd.c
> > +++ b/drivers/block/paride/pcd.c
...
> > -static int verbose = 0;
> > +static bool verbose = 0;
>
> This should be int. Verbose can be set to 2 for extra verbosity.
Again, I haven't made it more broken than it is already:
module_param(verbose, bool, 0644);
I've split these two off into separate fixes. Thanks!
> Btw, these patches that touch a ton of drivers are the wrong idea.
> If you ack any part of it, then get_maintainer.pl CCs you on every
> single kernel patch until eventually you get old and die.
I didn't know that; get_maintainer.pl usually produces too much spew for
me anyway. It could use some smarts.
Cheers,
Rusty.
next prev parent reply other threads:[~2012-01-04 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 3:18 Rusty Russell
2012-01-03 12:44 ` Dan Carpenter
2012-01-04 2:27 ` Rusty Russell [this message]
2012-01-03 12:58 ` Dan Carpenter
2012-01-03 13:17 ` [patch] TPM: handle errors from probe_itpm() Dan Carpenter
2012-01-04 2:29 ` [PATCH] intelfbdrv.c: bailearly is an int module_param Rusty Russell
2012-01-04 2:30 ` [PATCH] paride/pcd: fix bool verbose module parameter Rusty Russell
2012-01-04 7:12 ` [PATCH 12/15] module_param: make bool parameters really bool (drivers & misc) Tomi Valkeinen
2012-01-05 0:03 ` Rusty Russell
2012-01-06 12:31 ` Geert Uytterhoeven
2012-01-09 6:26 ` Rusty Russell
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=8762gsdwwo.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pawel.moll@arm.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
Powered by JetHome