From: Joe Perches <joe@perches.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Anatolij Gustschin <agust@denx.de>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Jeff Garzik <jgarzik@pobox.com>,
kernel-janitors@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] drivers/ata/pata_mpc52xx.c: add missing kfree
Date: Sat, 10 Mar 2012 11:22:40 -0800 [thread overview]
Message-ID: <1331407360.1762.8.camel@joe2Laptop> (raw)
In-Reply-To: <20120310184407.GB4139@pengutronix.de>
On Sat, 2012-03-10 at 19:44 +0100, Wolfram Sang wrote:
> > Anatolij is not listed as a maintainer for this file
> > nor has he ever written or signed a patch for it.
> I noticed that Grant was in CC, assumed that it was because of his previous MPC
> maintainership and mentioned that Anatolij took over. Nothing more, just wanted
> to help.
Actually, it's because there's a K: of_get_property
line in OPEN FIRMWARE and the file has one.
I suppose that get_maintainers could be told to
ignore K: entries when using -f <file>.
> > It'd be possible to add patterns to MAINTAINERS
> > if Anatolij really wants to see changes to drivers.
> It seems a bit too much for my taste (hardly readable? false positives?),
There are no false positives as far as I can tell.
Just using *mpc5* doesn't give any either today.
It's perlish so the whole thing is gibberish anyway.
next prev parent reply other threads:[~2012-03-10 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 17:56 [PATCH] drivers/ata/pata_mpc52xx.c: add missing kfree Julia Lawall
2012-03-10 18:13 ` Wolfram Sang
2012-03-10 18:32 ` Joe Perches
2012-03-10 18:44 ` Wolfram Sang
2012-03-10 19:22 ` Joe Perches [this message]
2012-03-10 18:32 ` walter harms
2012-03-10 21:50 ` Julia Lawall
[not found] ` <1331402199-8000-1-git-send-email-Julia.Lawall-L2FTfq7BK8M@public.gmane.org>
2012-03-11 10:04 ` Sergei Shtylyov
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=1331407360.1762.8.camel@joe2Laptop \
--to=joe@perches.com \
--cc=Julia.Lawall@lip6.fr \
--cc=agust@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jgarzik@pobox.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=w.sang@pengutronix.de \
/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