linux-kernel - Re: [PATCH] regulator: Ensure unique regulator debugfs directory names

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:	Tue, 18 Nov 2014 10:04:33 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
	Alan Tull <atull@...nsource.altera.com>
Subject: Re: [PATCH] regulator: Ensure unique regulator debugfs directory
 names

On Mon, Nov 17, 2014 at 08:18:44PM -0800, Guenter Roeck wrote:

> Sorry, I have no idea how you expect me (and others) to handle situations
> like this, much less with this patch. Please keep in mind that this is
> a per-maintainer process, and each maintainer handles things differently.
> Individual maintainers may expect me to send a ping like I did, or to
> resend the patch, or they may not reply because they dislike the patch

The default process is to resend the patch; I'm sure there are some
people who won't like that for some reason but it's reasonably rare.

> and they don't want to be bothered with a discussion. Some even go
> ballistic if they get an e-mail with more than 80 columns of text.

That's going to annoy essentially everyone, some people will be more
vocal than others but it's just a pretty basic thin.

> I can't even find out by browsing the regulator mailing list since it
> appears that there is no such list.

lkml.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)