From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Tejun Heo <tj@kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] wm8960: fix compile error
Date: Tue, 20 Jul 2010 16:18:52 +0100 [thread overview]
Message-ID: <20100720151852.GA20241@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <AANLkTinTT3_yy02wGJfKwannKT2rrZN899JKrdlvtLz7@mail.gmail.com>
On Tue, Jul 20, 2010 at 11:02:37PM +0800, Axel Lin wrote:
> 2010/7/20 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> > but please do try to bear in mind the feedback you've previously been
> > given about formatting your patches so they can be easily applied. You
> I'm a little bit confused about the meaning of "formatting your patches"?
> Do you mean my patches cannot be applied by git am command? or?
> ( I tried the git am command with the mail I sent and it looks ok )
In this case the main thing is the subject line which is not consistent
with other subject lines for patches in this area of code. This sort of
stuff is particularly important when you're submitting large numbers of
very small fixes.
> > probably also want to look at the CC list for your patches, I'm not sure
> > why you're CCing Tejun here.
> I get the CC list by get_maintainer.pl. Looks like the script gives me wrong
> CC list.
Yes, you need to apply a bit of taste to the output - it's inclined to
generate false positives. For matches from MAINTAINERS it's good but
for things generated from the git logs it can easily miss people or pick
up people who've been doing kernel wide cleanup work.
prev parent reply other threads:[~2010-07-20 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 9:49 [PATCH] wm8960: fix compile error Axel Lin
2010-07-20 11:07 ` Mark Brown
2010-07-20 15:02 ` Axel Lin
2010-07-20 15:18 ` Mark Brown [this message]
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=20100720151852.GA20241@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=tj@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