From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: kernel-janitors@vger.kernel.org,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <npalix.work@gmail.com>,
cocci@diku.dk, linux-kernel@vger.kernel.org, mmarek@suse.cz
Subject: Re: [PATCH 1/2] scripts/coccinelle: semantic patches related to
Date: Tue, 27 Dec 2011 17:10:33 +0000 [thread overview]
Message-ID: <20111227171032.GA22729@sirena.org.uk> (raw)
In-Reply-To: <1325004092-28162-1-git-send-email-julia.lawall@lip6.fr>
On Tue, Dec 27, 2011 at 05:41:31PM +0100, Julia Lawall wrote:
> From: Julia Lawall <Julia.Lawall@lip6.fr>
>
> From: Julia Lawall <Julia.Lawall@lip6.fr>
Something went wrong here?
> devm_ functions allocate memory that is to remain allocated until the
> device is detached. This patch checks for opportunities for using the
> function devm_request_and_ioremap.
Note that devm_request_and_ioremap() is scheduled for merge in 3.3 so
patches based on this should probably wait until after that has been
merged.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: kernel-janitors@vger.kernel.org,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <npalix.work@gmail.com>,
cocci@diku.dk, linux-kernel@vger.kernel.org, mmarek@suse.cz
Subject: Re: [PATCH 1/2] scripts/coccinelle: semantic patches related to devm_ functions
Date: Tue, 27 Dec 2011 17:10:33 +0000 [thread overview]
Message-ID: <20111227171032.GA22729@sirena.org.uk> (raw)
In-Reply-To: <1325004092-28162-1-git-send-email-julia.lawall@lip6.fr>
On Tue, Dec 27, 2011 at 05:41:31PM +0100, Julia Lawall wrote:
> From: Julia Lawall <Julia.Lawall@lip6.fr>
>
> From: Julia Lawall <Julia.Lawall@lip6.fr>
Something went wrong here?
> devm_ functions allocate memory that is to remain allocated until the
> device is detached. This patch checks for opportunities for using the
> function devm_request_and_ioremap.
Note that devm_request_and_ioremap() is scheduled for merge in 3.3 so
patches based on this should probably wait until after that has been
merged.
next prev parent reply other threads:[~2011-12-27 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 16:30 [PATCH 1/2] scripts/coccinelle: semantic patches related to devm_ functions Julia Lawall
2011-12-27 16:30 ` Julia Lawall
2011-12-27 16:41 ` Julia Lawall
2011-12-27 16:41 ` Julia Lawall
2011-12-27 17:10 ` Mark Brown [this message]
2011-12-27 17:10 ` Mark Brown
2012-01-14 21:45 ` Michal Marek
2012-01-14 21:45 ` Michal Marek
2011-12-27 17:19 ` Julia Lawall
2011-12-27 17:28 ` Julia Lawall
2011-12-27 17:28 ` Julia Lawall
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=20111227171032.GA22729@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@diku.dk \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=npalix.work@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.