linux-kernel - Re: [PATCH v2] cpufreq: Reformat printk() statements

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: <1394558212.21085.57.camel@joe-AO722>
Date:	Tue, 11 Mar 2014 10:16:52 -0700
From:	Joe Perches <joe@...ches.com>
To:	Dirk Brandewie <dirk.brandewie@...il.com>
Cc:	Soren Brinkmann <soren.brinkmann@...inx.com>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>, cpufreq@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v2] cpufreq: Reformat printk() statements

On Tue, 2014-03-11 at 10:13 -0700, Dirk Brandewie wrote:
> On 03/11/2014 10:03 AM, Soren Brinkmann wrote:
> > From: Joe Perches <joe@...ches.com>
> >   - Add missing newlines
> >   - Coalesce format fragments
> >   - Convert printks to pr_<level>
> >   - Align arguments
> This introduces a bunch of lines over 80 charaters long.

Intentionally.

from: Documentation/CodingStyle

		Chapter 2: Breaking long lines and strings

Coding style is all about readability and maintainability using commonly
available tools.

[]

never break user-visible strings such as
printk messages, because that breaks the ability to grep for them.


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