public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
	linux-mtd@lists.infradead.org,
	Mike Frysinger <vapier.adi@gmail.com>,
	kernel@pengutronix.de, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 2/2] mtd/uclinux: add a comment about why uclinux_ram_map must not be static
Date: Mon, 15 Oct 2012 14:15:34 +1000	[thread overview]
Message-ID: <507B8DE6.6030407@snapgear.com> (raw)
In-Reply-To: <1350027693-19528-2-git-send-email-u.kleine-koenig@pengutronix.de>

On 12/10/12 17:41, Uwe Kleine-König wrote:
> I was (at least) the second person trying to fix a warning by sparse, so
> document in the code why this is a bad idea.
>
> Signed-off-by: Uwe Kleine-K÷nig <u.kleine-koenig@pengutronix.de>

Acked-by: Greg Ungerer <gerg@uclinux.org>


> ---
> Hello,
>
> it's a bit exaggerated to claim that sparse is happy now, but at least
> we have one warning less :-)
>
> Uwe
>   drivers/mtd/maps/uclinux.c |    6 ++++++
>   1 file changed, 6 insertions(+)
>
> diff --git a/drivers/mtd/maps/uclinux.c b/drivers/mtd/maps/uclinux.c
> index f5e8e9a..18cf6d0 100644
> --- a/drivers/mtd/maps/uclinux.c
> +++ b/drivers/mtd/maps/uclinux.c
> @@ -23,6 +23,12 @@
>
>   /****************************************************************************/
>
> +/*
> + * Blackfin uses uclinux_ram_map during startup, so it must not be static.
> + * Provide a dummy declaration to make sparse happy.
> + */
> +extern struct map_info uclinux_ram_map;
> +
>   struct map_info uclinux_ram_map = {
>   	.size = 0,
>   };
>


-- 
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

  parent reply	other threads:[~2012-10-15  4:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 15:25 [PATCH] [RFC] mtd/uclinux: support ROM and allow passing the base address Uwe Kleine-König
2012-10-09  3:29 ` Greg Ungerer
2012-10-09  8:44   ` Uwe Kleine-König
2012-10-09 10:37     ` Greg Ungerer
2012-10-10  7:58       ` Uwe Kleine-König
2012-10-12  4:46       ` Mike Frysinger
2012-10-12  5:57         ` Greg Ungerer
2012-10-12  7:22           ` Uwe Kleine-König
2012-10-12 16:09             ` Mike Frysinger
2012-10-12 16:22               ` Mike Frysinger
2012-10-15 14:00           ` Artem Bityutskiy
2012-10-11  4:21 ` Mike Frysinger
2012-10-11  6:13   ` Uwe Kleine-König
2012-10-12  7:41   ` Uwe Kleine-König
2012-10-12 16:18     ` Mike Frysinger
2012-10-12  7:41 ` [PATCH 1/2 RFC v2] " Uwe Kleine-König
2012-10-12  7:41   ` [PATCH 2/2] mtd/uclinux: add a comment about why uclinux_ram_map must not be static Uwe Kleine-König
2012-10-12 16:23     ` Mike Frysinger
2012-10-15  4:15     ` Greg Ungerer [this message]
2012-10-15  4:14   ` [PATCH 1/2 RFC v2] mtd/uclinux: support ROM and allow passing the base address Greg Ungerer
2012-10-15  6:58     ` Uwe Kleine-König
2012-10-16  1:13       ` Greg Ungerer
2012-10-16  6:56         ` Uwe Kleine-König

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=507B8DE6.6030407@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=gerg@uclinux.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=vapier.adi@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