From: Joe Perches <joe@perches.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Daniel Walker <dwalker@codeaurora.org>,
Liam Girdwood <lrg@slimlogic.co.uk>,
linux-kernel@vger.kernel.org, bleong@codeaurora.org
Subject: Re: [PATCH 2/2] drivers: regulator: core: convert to using pr_ macros
Date: Thu, 18 Nov 2010 08:29:15 -0800 [thread overview]
Message-ID: <1290097755.1817.13.camel@Joe-Laptop> (raw)
In-Reply-To: <20101118132929.GD7233@rakim.wolfsonmicro.main>
On Thu, 2010-11-18 at 13:29 +0000, Mark Brown wrote:
> On Wed, Nov 17, 2010 at 04:36:51PM -0800, Joe Perches wrote:
> > (rest of original patch below, but no additional comments)
> Don't do that, trim unneeded context from your mails. This makes it
> much easier to find the actual content you've written and is much nicer
> for those of us who work on mobile connections.
If you check history, you'll find I'm consistent in doing
just that, including trimming blank lines from quoted.
This was an exceptional case because quoting the original
and declaring "no additional comments" allows Daniel to
see the changes he could make in place.
next prev parent reply other threads:[~2010-11-18 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 23:30 [PATCH 1/2] drivers: regulator: core: use pr_fmt Daniel Walker
2010-11-17 23:30 ` [PATCH 2/2] drivers: regulator: core: convert to using pr_ macros Daniel Walker
2010-11-18 0:36 ` Joe Perches
2010-11-18 1:30 ` Joe Perches
2010-11-18 13:30 ` Mark Brown
2010-11-18 13:29 ` Mark Brown
2010-11-18 16:29 ` Joe Perches [this message]
2010-11-18 0:29 ` [PATCH 1/2] drivers: regulator: core: use pr_fmt Joe Perches
2010-11-18 0:35 ` Daniel Walker
2010-11-18 10:37 ` Mark Brown
2010-11-18 16:44 ` Joe Perches
2010-11-18 10:35 ` Mark Brown
2010-11-19 11:09 ` Liam Girdwood
2010-11-19 17:07 ` Joe Perches
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=1290097755.1817.13.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=bleong@codeaurora.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dwalker@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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