linux-kernel - Re: [PATCH 2/2] ttyprintk: Allow built as a module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 03 Apr 2014 08:13:46 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Jiri Slaby <jslaby@...e.cz>, Samo Pogacnik <samo_pogacnik@....net>,
	Arnd Bergmann <arnd@...db.de>, Jean Delvare <jdelvare@...e.de>,
	Struan Bartlett <struan.bartlett@...il.com>,
	Andreas Schwab <schwab@...ux-m68k.org>,
	gnomes@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] ttyprintk: Allow built as a module

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@...e.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/