ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] No more module removal -- Unconference track
Date: Tue, 19 Aug 2014 17:54:26 +0200	[thread overview]
Message-ID: <s5hioloscel.wl-tiwai@suse.de> (raw)
In-Reply-To: <20140819152350.GE11085@thunk.org>

At Tue, 19 Aug 2014 11:23:50 -0400,
Theodore Ts'o wrote:
> 
> On Tue, Aug 19, 2014 at 07:55:47AM -0700, Guenter Roeck wrote:
> > On Tue, Aug 19, 2014 at 10:48:39AM -0400, Theodore Ts'o wrote:
> > > This has been scheduled at 2pm at the request of Rusty.  (Reminder: if
> > > you're going to propose a topic, please send e-mail to start a thread
> > > on ksummit-discuss).
> > > 
> > Do we have a context ? I am using insert/remove module a lot during testing,
> > and would hate to see it go. It also permits module updates without having to
> > reboot the kernel. There must be lots of other reasons to support module
> > removal. So I would really dislike if it was no longer available, and I don't
> > really see the point.
> 
> Rusty has been trying to nuke module removal for years.
> 
> Unfortunately, it's been incredibly useful for many reasons.
> 
> In addition to the reasons you've suggested, it's the only way that I
> can reset a malfunctioning sound driver without rebooting, and I'd
> hate to have to regress to windows style "reboot to fix the problem".

Oh, please report such a problem.

Or wait, maybe we shouldn't debug it for keeping one more vote for the
election "save module removal" :)


Takashi

  parent reply	other threads:[~2014-08-19 15:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 14:48 Theodore Ts'o
2014-08-19 14:55 ` Guenter Roeck
2014-08-19 15:23   ` Theodore Ts'o
2014-08-19 15:40     ` Dan Carpenter
2014-08-19 15:47       ` Guenter Roeck
2014-08-19 16:09         ` Dan Carpenter
2014-08-19 16:34           ` Martin K. Petersen
2014-08-19 16:59           ` Rik van Riel
2014-08-19 17:19           ` Guenter Roeck
2014-08-19 16:43         ` David Woodhouse
2014-08-19 17:13           ` Grant Likely
2014-08-19 17:23             ` David Woodhouse
2014-08-19 15:54     ` Takashi Iwai [this message]
2014-08-25 11:01   ` Masami Hiramatsu
2014-08-25 11:05     ` Jiri Kosina
2014-08-26  5:24       ` Masami Hiramatsu
2014-08-27 23:05         ` Theodore Ts'o
2014-08-26 21:39   ` David Howells
2014-08-26 21:45     ` Jiri Kosina
2014-08-27  6:43       ` Masami Hiramatsu

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=s5hioloscel.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=ksummit-discuss@lists.linux-foundation.org \
    --cc=tytso@mit.edu \
    /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