From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] video: pxa168fb: remove a redundant pxa168fb_check_var call
Date: Fri, 21 Jan 2011 18:33:04 +0000 [thread overview]
Message-ID: <20110121183304.GA3075@sirena.org.uk> (raw)
In-Reply-To: <201101211907.07386.marek.vasut@gmail.com>
On Fri, Jan 21, 2011 at 07:07:07PM +0100, Marek Vasut wrote:
> Please, don't use the get_maintainers script. This CCs too many people, really.
*Using* get_maintainers.pl is fine, but it is important to apply taste
to the results since as you say it does generate false positives.
prev parent reply other threads:[~2011-01-21 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1295608686.3976.9.camel@phoenix>
2011-01-21 18:07 ` [PATCH] video: pxa168fb: remove a redundant pxa168fb_check_var call Marek Vasut
2011-01-21 18:33 ` 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=20110121183304.GA3075@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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