From: Takashi Iwai <tiwai@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
Samo Pogacnik <samo_pogacnik@t-2.net>,
Arnd Bergmann <arnd@arndb.de>, Jean Delvare <jdelvare@suse.de>,
Struan Bartlett <struan.bartlett@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
gnomes@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ttyprintk: Allow built as a module
Date: Thu, 03 Apr 2014 08:13:46 +0200 [thread overview]
Message-ID: <s5ha9c3djol.wl%tiwai@suse.de> (raw)
In-Reply-To: <20140402193222.GA26425@kroah.com>
At Wed, 2 Apr 2014 12:32:22 -0700,
Greg Kroah-Hartman wrote:
>
> On Wed, Apr 02, 2014 at 12:29:42PM +0200, Takashi Iwai wrote:
> > The driver is well written to be used as a module, just the exit call
> > is missing.
> >
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> > drivers/char/Kconfig | 2 +-
> > drivers/char/ttyprintk.c | 13 ++++++++++++-
> > 2 files changed, 13 insertions(+), 2 deletions(-)
>
> There was some reason we didn't do this back when the code was accepted,
> but I really can't remember why.
>
> If you have tested this out, I don't have any objections to taking these
> patches, thanks.
The module worked fine with my quick tests (load/unload/feed something
via /dev/ttyprintk), at least. But it'd be helpful if anyone
remembers and clarifies.
thanks,
Takashi
next prev parent reply other threads:[~2014-04-03 6:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 10:29 [PATCH 1/2] ttyprintk: Fix wrong tty_unregister_driver() call in the error path Takashi Iwai
2014-04-02 10:29 ` [PATCH 2/2] ttyprintk: Allow built as a module Takashi Iwai
2014-04-02 12:31 ` Jean Delvare
2014-04-02 12:42 ` Takashi Iwai
2014-04-02 19:32 ` Greg Kroah-Hartman
2014-04-03 6:13 ` Takashi Iwai [this message]
2014-04-05 11:15 ` Samo Pogačnik
2014-04-02 12:24 ` [PATCH 1/2] ttyprintk: Fix wrong tty_unregister_driver() call in the error path Jean Delvare
2014-04-03 6:10 ` Takashi Iwai
2014-04-03 8:00 ` Jiri Slaby
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=s5ha9c3djol.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=arnd@arndb.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.de \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=samo_pogacnik@t-2.net \
--cc=schwab@linux-m68k.org \
--cc=struan.bartlett@gmail.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
all inboxes | Powered by JetHome®