From: Mark Brown <broonie@kernel.org>
To: Nenghua Cao <nhcao@marvell.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] driver: regmap: add regmap_parse_val api
Date: Wed, 5 Mar 2014 10:03:26 +0800 [thread overview]
Message-ID: <20140305020326.GT13126@sirena.org.uk> (raw)
In-Reply-To: <53145D05.60207@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
On Mon, Mar 03, 2014 at 06:44:21PM +0800, Nenghua Cao wrote:
> Do you have any comments about these two patches? Thanks!
I've not looked at it yet, please don't nag - one of the reasons it got
bumped down my priority list is that you nagged previously. I tend to
do this partly as a function of looking at the nag making me feel like I
looked at the code and partly as a deliberate method for discouraging
nags.
Looking at this I do also notice that you didn't use a subject line
matching the style for the subsystem which means it's going to be less
likely to be looked at. Patches that aren't for subsystems I maintain
tend to get a lower priority.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-05 2:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:44 Nenghua Cao
2014-02-20 8:24 ` Nenghua Cao
2014-02-20 8:55 ` Mark Brown
2014-02-20 12:09 ` Nenghua Cao
2014-02-20 13:42 ` Mark Brown
2014-03-03 10:44 ` Nenghua Cao
2014-03-05 2:03 ` Mark Brown [this message]
2014-03-06 9:41 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2014-02-19 5:19 Nenghua Cao
2014-02-19 5:28 ` Nenghua Cao
2014-02-19 7:50 ` Mark Brown
2014-02-19 10:50 ` Nenghua Cao
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=20140305020326.GT13126@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhcao@marvell.com \
/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
all inboxes | Powered by JetHome®