From: Andrew Morton <akpm@linux-foundation.org>
To: Zev Weiss <zevweiss@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] [MTD] physmap.c: Add a dummy release function
Date: Wed, 17 Sep 2008 12:01:29 -0700 [thread overview]
Message-ID: <20080917120129.f6d3544b.akpm@linux-foundation.org> (raw)
In-Reply-To: <48CB5EA4.10907@gmail.com>
> Subject: [PATCH 3/3] [MTD] physmap.c: Add a dummy release function
Please avoid putting the "MTD" inside the [] characters. Anything
which is inside [] is supposed to be discarded by the patch-receiving
party. This is for things like [rfc], [patch 3/12], [2.6.27-rc5], etc.
But we do want the "mtd" text to go all the way through into the
mainline git metadata.
On Fri, 12 Sep 2008 23:33:08 -0700
Zev Weiss <zevweiss@gmail.com> wrote:
>
> Adding a dummy release function to the physmap device so as to silence a log
> warning on initialization.
>
> Signed-off-by: Zev Weiss <zevweiss@gmail.com>
> ---
> drivers/mtd/maps/physmap.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/mtd/maps/physmap.c b/drivers/mtd/maps/physmap.c
> index 49e2039..73a8d3c 100644
> --- a/drivers/mtd/maps/physmap.c
> +++ b/drivers/mtd/maps/physmap.c
> @@ -277,11 +277,16 @@ static struct resource physmap_flash_resource = {
> .flags = IORESOURCE_MEM,
> };
>
> +static void physmap_dummy_release(struct device *dev)
> +{
> +}
> +
> static struct platform_device physmap_flash = {
> .name = "physmap-flash",
> .id = 0,
> .dev = {
> .platform_data = &physmap_flash_data,
> + .release = &physmap_dummy_release,
> },
> .num_resources = 1,
> .resource = &physmap_flash_resource,
Nope. Please see Documentation/kobject.txt - search for the text
"mocked mercilessly".
prev parent reply other threads:[~2008-09-17 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 6:33 [PATCH 3/3] [MTD] physmap.c: Add a dummy release function Zev Weiss
2008-09-13 10:47 ` Lennert Buytenhek
2008-09-13 11:24 ` Zev Weiss
2008-09-17 19:01 ` Andrew Morton [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=20080917120129.f6d3544b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=zevweiss@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox