linux-kernel - Re: [tip:x86/debug] printk: Make the printk*once() variants return a value

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]

Message-ID: <20160709075003.GA3822@pd.tnic>
Date:	Sat, 9 Jul 2016 09:50:03 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Joe Perches <joe@...ches.com>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	mingo@...nel.org, luto@...nel.org, hpa@...or.com,
	peterz@...radead.org, brgerst@...il.com,
	torvalds@...ux-foundation.org, tglx@...utronix.de,
	luto@...capital.net, dvlasenk@...hat.com, fweisbec@...il.com,
	jpoimboe@...hat.com, bp@...e.de, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/debug] printk: Make the printk*once() variants return a
 value

On Fri, Jul 08, 2016 at 07:40:48PM -0700, Joe Perches wrote:
> This change isn't described in the commit message and there
> doesn't seem to be a need to change this.

How do *you* know? Did *you* actually sit down and build a kernel with
your proposed change before sending a reply?

I'm pretty sure you didn't.

Well, there is a very good reason why I made that change but I'm not
going to tell you.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.