From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
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: Mon, 17 Nov 2014 20:18:44 -0800 [thread overview]
Message-ID: <546AC8A4.4030705@roeck-us.net> (raw)
In-Reply-To: <20141117232620.GA22111@sirena.org.uk>
On 11/17/2014 03:26 PM, Mark Brown wrote:
> On Mon, Nov 17, 2014 at 01:00:09PM -0800, Guenter Roeck wrote:
>> On Fri, Oct 17, 2014 at 08:17:03AM -0700, Guenter Roeck wrote:
>
>>> To avoid the problem, prepend the debugfs directory name for a regulator
>>> with its parent device name if available, but only if no explicit
>>> regulator name was provided.
>
>> Hi Mark,
>>
>> did you have time to look into this patch ?
>
> Please don't send contentless, quoted pings. One of two things will be
> true: either your patch got lost in which case a quoted copy is of no
> use in getting the patch applied or the patch is buried under other mail
> in which case you are at best adding to the email volume and at worst
> your mail will never be seen as it's threaded in with the original send.
>
Hi Mark,
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
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.
Negotiating a minefield sometimes seems easier than submitting kernel
patches :-(.
I can't even find out by browsing the regulator mailing list since it
appears that there is no such list.
Guenter
next prev parent reply other threads:[~2014-11-18 4:18 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 [this message]
2014-11-18 10:04 ` Mark Brown
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=546AC8A4.4030705@roeck-us.net \
--to=linux@roeck-us.net \
--cc=atull@opensource.altera.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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