public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: mahatma@eu.by, linux-kernel@vger.kernel.org,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: #2 (Re: More modaliases + patchtool)
Date: Mon, 13 Sep 2010 12:54:28 +0930	[thread overview]
Message-ID: <201009131254.28773.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100911175118.GA8521@core.coreip.homeip.net>

On Sun, 12 Sep 2010 03:21:19 am Dmitry Torokhov wrote:
> On Sat, Sep 11, 2010 at 11:44:33AM +0930, Rusty Russell wrote:
> > On Thu, 19 Aug 2010 10:12:36 pm Dzianis Kahanovich wrote:
> > > diff -pruN a/drivers/char/sysrq.c b/drivers/char/sysrq.c
> > > --- a/drivers/char/sysrq.c	2010-08-02 01:11:14.000000000 +0300
> > > +++ b/drivers/char/sysrq.c	2010-08-19 15:23:41.444764991 +0300
> > > @@ -799,4 +799,9 @@ static int __init sysrq_init(void)
> > >  
> > >  	return 0;
> > >  }
> > > +
> > > +#ifdef CONFIG_INPUT
> > > +MODULE_DEVICE_TABLE(input, sysrq_ids);
> > > +#endif
> > > +
> > >  module_init(sysrq_init);
> > 
> > Hmm, Dmitry?  Do we want this auto-loaded?
> > 
> 
> Rusty,
> 
> CONFIG_MAGIC_SYSRQ is currently a bool and SysRq support can only be
> built-in.

That seems pretty clear then.

Thanks!
Rusty.
PS. Dmitry, maybe a build with allmodconfig would help eliminate some of
    these?

  reply	other threads:[~2010-09-13  3:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C6BE292.3060307@bspu.unibel.by>
2010-08-19  0:50 ` More modaliases + patchtool Rusty Russell
2010-08-19 14:58   ` #3 (Re: More modaliases + patchtool) Dzianis Kahanovich
     [not found]   ` <4C6D26BC.9040805@bspu.unibel.by>
2010-09-11  2:14     ` #2 " Rusty Russell
2010-09-11  3:36       ` Jeremy Fitzhardinge
2010-09-13  3:03         ` Rusty Russell
2010-09-11 17:51       ` Dmitry Torokhov
2010-09-13  3:24         ` Rusty Russell [this message]
2010-09-17 10:55       ` pci: Re: #2 (Re: More modaliases + patchtool)) Dzianis Kahanovich
2010-09-17 13:11       ` Dzianis Kahanovich
2010-09-17 13:26       ` xenbus: " Dzianis Kahanovich
2010-09-17 18:09         ` Jeremy Fitzhardinge
2010-09-17 13:27       ` usb: " Dzianis Kahanovich
2010-09-17 13:29       ` serio: " Dzianis Kahanovich
2010-09-17 13:29       ` pnp: " Dzianis Kahanovich
2010-09-17 13:32       ` of: " Dzianis Kahanovich
2010-09-17 13:35       ` i2c: " Dzianis Kahanovich
2010-09-17 14:06         ` Mark Brown
2010-09-17 15:47           ` Dzianis Kahanovich
2010-09-17 15:54             ` Mark Brown
2010-09-17 13:36       ` hid: " Dzianis Kahanovich
2010-09-17 13:36       ` dio: " Dzianis Kahanovich
2010-09-17 13:37       ` ccw: " Dzianis Kahanovich
2010-09-17 13:38       ` acpi: " Dzianis Kahanovich
2010-09-17 13:38       ` spi " Dzianis Kahanovich
2010-09-17 13:39       ` RapidIO: " Dzianis Kahanovich
2010-09-17 13:42       ` platform: " Dzianis Kahanovich
2010-09-17 13:54         ` Mark Brown
2010-09-17 15:55       ` acpi (signed): " Dzianis Kahanovich
2010-09-16 20:23 #2 (Re: More modaliases + patchtool) Denis Kaganovich

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=201009131254.28773.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahatma@eu.by \
    /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