From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Alan Tull <atull@opensource.altera.com>
Subject: Re: [PATCH] regulator: Ensure unique regulator debugfs directory names
Date: Tue, 18 Nov 2014 10:04:33 +0000 [thread overview]
Message-ID: <20141118100433.GH22111@sirena.org.uk> (raw)
In-Reply-To: <546AC8A4.4030705@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-11-18 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 15:17 Guenter Roeck
2014-11-17 21:00 ` Guenter Roeck
2014-11-17 23:26 ` Mark Brown
2014-11-18 4:18 ` Guenter Roeck
2014-11-18 10:04 ` Mark Brown [this message]
2015-03-27 23:14 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141118100433.GH22111@sirena.org.uk \
--to=broonie@kernel.org \
--cc=atull@opensource.altera.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome