From: Rusty Russell <rusty@rustcorp.com.au>
To: paulmck@linux.vnet.ibm.com
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>
Subject: Re: [PATCH 10/15] module_param: make bool parameters really bool (core code)
Date: Mon, 19 Dec 2011 12:50:59 +1030 [thread overview]
Message-ID: <87ty4xnvxw.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20111216195830.GH2419@linux.vnet.ibm.com>
On Fri, 16 Dec 2011 11:58:30 -0800, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> On Thu, Dec 15, 2011 at 01:43:24PM +1030, Rusty Russell wrote:
> > module_param(bool) used to counter-intuitively take an int. In
> > fddd5201 (mid-2009) we allowed bool or int/unsigned int using a messy
> > trick.
> >
> > It's time to remove the int/unsigned int option. For this version
> > it'll simply give a warning, but it'll break next kernel version.
> >
> > Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
>
> For the rcutorture component:
>
> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Tested-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> Given that this portion of the patch is self-sufficient, I have queued
> the rcutorture portion of this patch with your signed-off-by, which I
> can push for either 3.3 or 3.4 (default is most likely 3.4). Of course,
> if you would prefer some other approach, please let me know.
Nope, more than happy. Have removed it from my patch.
Cheers,
Rusty.
prev parent reply other threads:[~2011-12-19 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 3:13 [PATCH 10/15] module_param: make bool parameters really bool (core code) Rusty Russell
2011-12-16 19:58 ` Paul E. McKenney
2011-12-19 2:20 ` Rusty Russell [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=87ty4xnvxw.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.