linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Greg KH <greg@kroah.com>,
	"Pete Zaitcev (Red Hat, Inc.)" <zaitcev@redhat.com>
Subject: Re: linux-next: manual merge of the boot-params tree
Date: Tue, 30 Dec 2008 07:52:01 +1030	[thread overview]
Message-ID: <200812300752.02671.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20081230011055.d2f6ced2.sfr@canb.auug.org.au>

On Tuesday 30 December 2008 00:40:55 Stephen Rothwell wrote:
> Hi Rusty,
> 
> Today's linux-next merge of the boot-params tree got a conflict in
> drivers/usb/core/usb.c between commit
> 6e7b5429a08fe4f71c336710bd45acdce6cd3df7 ("USB: don't use
> __module_param_call") from the usb tree and commit
> 9634765245cd7aba71328c71813ca882d008632d ("USB: Don't use
> __module_param_call; use core_param") from the boot-params tree.
> 
> Two different versions of the same change?  I fixed it up (used the
> boot-params tree version) and can carry the fix as necessary.  It sounds
> like Greg should drop the patch from the usb tree (or pick up the version
> from the boot-params tree).

Yes; I sent Greg an email but it might have been lost in the flood.  Pete
acked.

I'd rather this version for simplicity in the other patches, but I can live
if not.  It's also a little clearer, IMHO.

Thanks,
Rusty.

>From 9634765245cd7aba71328c71813ca882d008632d Mon Sep 17 00:00:00 2001
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Thu, 25 Dec 2008 22:06:14 +1030
Subject: [PATCH] USB: Don't use __module_param_call; use core_param.

Impact: cleanup

Found this when I changed args to __module_param_call.  We now have
core_param for exactly this, but Greg assures me "nousb" is used as a
module parameter, so we need the #ifdef MODULE.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Cc: Pete Zaitcev <zaitcev@redhat.com>

diff --git a/drivers/usb/core/usb.c b/drivers/usb/core/usb.c
index be1fa07..74d9dcd 100644
--- a/drivers/usb/core/usb.c
+++ b/drivers/usb/core/usb.c
@@ -962,8 +962,12 @@ void usb_buffer_unmap_sg(const struct usb_device *dev, int is_in,
 }
 EXPORT_SYMBOL_GPL(usb_buffer_unmap_sg);
 
-/* format to disable USB on kernel command line is: nousb */
-__module_param_call("", nousb, param_set_bool, param_get_bool, &nousb, 0444);
+/* To disable USB, kernel command line is 'nousb' not 'usbcore.nousb' */
+#ifdef MODULE
+module_param(nousb, bool, 0444);
+#else
+core_param(nousb, nousb, bool, 0444);
+#endif
 
 /*
  * for external read access to <nousb>

  reply	other threads:[~2008-12-29 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 14:10 linux-next: manual merge of the boot-params tree Stephen Rothwell
2008-12-29 21:22 ` Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-29 14:22 Stephen Rothwell
2008-12-29 14:01 Stephen Rothwell
2008-12-18  9:35 Stephen Rothwell
2008-12-15 13:21 Stephen Rothwell
2008-12-15 13:21 Stephen Rothwell
2008-12-15 13:20 Stephen Rothwell
2008-12-15 13:20 Stephen Rothwell

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=200812300752.02671.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=greg@kroah.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=zaitcev@redhat.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;
as well as URLs for NNTP newsgroup(s).