linux-kernel - Re: [PATCH 2/9] ext4: Use pr_fmt and pr

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: <20120319.135342.859237474072712585.davem@davemloft.net>
Date:	Mon, 19 Mar 2012 13:53:42 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	tytso@....edu
Cc:	joe@...ches.com, adilger.kernel@...ger.ca,
	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/9] ext4: Use pr_fmt and pr_<level>

From: "Ted Ts'o" <tytso@....edu>
Date: Mon, 19 Mar 2012 11:31:34 -0400

> And in the past we've always allowed for local variations of style;
> it's never been a strict style nazism.  Linus has always given
> maintainers latitude and has frowned on patch churn for churn's sake.

The variations in opinion and taste are why it's important for
us to discuss the interfaces and tweak them so that most people
are happy with them and then everyone uses them.

Your story about get_fs() still being around isn't a victory,
or an accomplishment, it's just a small failure that we've been
too lazy to fix.  But it's one that if someone did post a patch
for it, would be accepted.

And the thing you call churn, I call development and progress.

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