linux-kernel - Re: [Announce] Linux-tiny project revival

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:	Fri, 28 Sep 2007 10:39:06 +0200
From:	Bernd Petrovitsch <bernd@...mix.at>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Indan Zupancic <indan@....nu>, Rob Landley <rob@...dley.net>,
	Michael Opdenacker <michael@...e-electrons.com>,
	linux-tiny@...enic.com,
	CE Linux Developers List <celinux-dev@...e.celinuxforum.org>,
	linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Announce] Linux-tiny project revival

On Fre, 2007-09-28 at 00:21 +0200, Arnd Bergmann wrote:
> On Thursday 27 September 2007, you wrote:
> > > Then you don't have to change every single printk in the kernel, but
> > > only those that don't currently come with a log level. More importantly,
> > > you can do the conversion without a flag day, by spreading (an empty)
> > > PRINTK_CONTINUED in places that do need a printk without a log level.
> > 
> > The problem is, how do you know whether to print a continued printk or not?
> > It depends on the loglevel of the first printk.
> 
> Those need to be looked at individually. You can normally see easily from

If think you misunderstood:
Say, you compile out everything of DEBUG level.
Say, you have a continued printk() after each and every pr_debug().

Then how is the macro supposed to know (at compile-time) that the
continued printk()  actually belongs to a DEBUG printk (and not another
one)?

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


-
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/