All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@linux-foundation.org, dwmw2@infradead.org,
	linux-kernel@vger.kernel.org, dhowells@redhat.com
Subject: Re: [PATCH] FRV: Fix a warning due to an unnecessary #include of an MTD header
Date: Wed, 1 Jul 2009 14:07:05 -0700	[thread overview]
Message-ID: <20090701140705.46481737.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090630212425.19244.37019.stgit@warthog.procyon.org.uk>

On Tue, 30 Jun 2009 22:24:25 +0100
David Howells <dhowells@redhat.com> wrote:

> Fix a warning due to an unnecessary #inclusion of linux/mtd/partitions:
> 
>   CC      arch/frv/mb93090-mb00/flash.o
> In file included from arch/frv/mb93090-mb00/flash.c:15:
> include/linux/mtd/partitions.h:50: warning: 'struct mtd_info' declared inside parameter list
> include/linux/mtd/partitions.h:50: warning: its scope is only this definition or declaration, which is probably not what you want
> include/linux/mtd/partitions.h:51: warning: 'struct mtd_info' declared inside parameter list
> include/linux/mtd/partitions.h:61: warning: 'struct mtd_info' declared inside parameter list
> include/linux/mtd/partitions.h:67: warning: 'struct mtd_info' declared inside parameter list

hm.  Maybe fix include/linux/mtd/partitions.h?

>  arch/frv/mb93090-mb00/flash.c |    1 -

That file isn't in mainline or linux-next afacit.

  reply	other threads:[~2009-07-01 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 21:24 [PATCH] FRV: Fix a warning due to an unnecessary #include of an MTD header David Howells
2009-07-01 21:07 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-30 21:16 David Howells
2009-06-30 21:26 ` David Howells

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=20090701140705.46481737.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.