From: David Miller <davem@davemloft.net>
To: julia@diku.dk
Cc: kernel-janitors@vger.kernel.org, eric.dumazet@gmail.com,
tj@kernel.org, jpirko@redhat.com, geert@linux-m68k.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] drivers/net/a2065.c: Convert release_resource to release_region/release_mem_region
Date: Wed, 23 Mar 2011 14:10:59 -0700 (PDT) [thread overview]
Message-ID: <20110323.141059.27811716.davem@davemloft.net> (raw)
In-Reply-To: <1300814123-25314-3-git-send-email-julia@diku.dk>
From: Julia Lawall <julia@diku.dk>
Date: Tue, 22 Mar 2011 18:15:23 +0100
> Request_mem_region should be used with release_mem_region, not
> release_resource.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
...
> Signed-off-by: Julia Lawall <julia@diku.dk>
Applied.
prev parent reply other threads:[~2011-03-23 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 17:15 [PATCH 3/3] drivers/net/a2065.c: Convert release_resource to release_region/release_mem_region Julia Lawall
2011-03-23 21:10 ` David Miller [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=20110323.141059.27811716.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jpirko@redhat.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).