linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-mtd@lists.infradead.org, linux-next@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Marc Zyngier <Marc.Zyngier@arm.com>,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH -next] mtd: fix physmap.h warnings
Date: Tue, 24 May 2011 10:40:34 +0300	[thread overview]
Message-ID: <1306222834.2785.53.camel@localhost> (raw)
In-Reply-To: <20110524074020.GA9490@flint.arm.linux.org.uk>

On Tue, 2011-05-24 at 08:40 +0100, Russell King wrote:
> On Tue, May 24, 2011 at 08:58:03AM +0300, Artem Bityutskiy wrote:
> > On Tue, 2011-05-24 at 08:53 +0300, Artem Bityutskiy wrote:
> > > On Mon, 2011-05-23 at 11:37 -0700, Randy Dunlap wrote:
> > > > From: Randy Dunlap <randy.dunlap@oracle.com>
> > > > 
> > > > Fix build warnings in physmap.h:
> > > > 
> > > > include/linux/mtd/physmap.h:25: warning: 'struct platform_device' declared inside parameter list
> > > > include/linux/mtd/physmap.h:25: warning: its scope is only this definition or declaration, which is probably not what you want
> > > > include/linux/mtd/physmap.h:26: warning: 'struct platform_device' declared inside parameter list
> > > > include/linux/mtd/physmap.h:27: warning: 'struct platform_device' declared inside parameter list
> > > > 
> > > > Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> > > 
> > > Oh, this was missed during review.  This was introduced in
> > > b7281ca2a4b00044c60c25059f467d05772cdbe3 which is going in via Russel's
> > > tree, so I guess Russel could pick up your patch.
> > 
> > My big apologies, s/Russel/Russell/.
> 
> Which patch?  Neither of these messages contained Randy's patch and I
> wasn't included on the original posting.

Sorry, I assumed you'd look that lkml is in CC and would find it in lkml
(I assumed you are subscribed there). I'll send this patch shortly.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2011-05-24  7:44 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23  5:45 linux-next: Tree for May 23 Stephen Rothwell
2011-05-23 16:42 ` linux-next: Tree for May 23 (infiniband + netlink) Randy Dunlap
     [not found]   ` <20110523094205.4a5651d2.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-05-23 18:05     ` Roland Dreier
2011-05-23 17:43 ` [PATCH -next] x86: apic_flat_64.c needs module.h Randy Dunlap
2011-05-23 17:51   ` Cyrill Gorcunov
2011-05-23 18:09     ` Cyrill Gorcunov
2011-05-23 18:12       ` Randy Dunlap
2011-05-23 18:35         ` Cyrill Gorcunov
2011-05-23 19:10         ` Ingo Molnar
2011-05-23 19:26           ` Ingo Molnar
2011-05-23 17:49 ` linux-next: Tree for May 23 (hwmon/coretemp.c) Randy Dunlap
2011-05-23 18:03   ` Guenter Roeck
2011-05-23 18:35 ` [PATCH -next] target: fix tfc_io.c printk format warning Randy Dunlap
2011-05-23 20:47   ` Nicholas A. Bellinger
2011-06-16 18:35     ` Randy Dunlap
2011-05-23 18:37 ` [PATCH -next] mtd: fix physmap.h warnings Randy Dunlap
2011-05-24  5:53   ` Artem Bityutskiy
2011-05-24  5:58     ` Artem Bityutskiy
2011-05-24  7:40       ` Russell King
2011-05-24  7:40         ` Artem Bityutskiy [this message]
2011-05-24  7:42         ` Artem Bityutskiy
2011-06-01  7:45           ` Artem Bityutskiy
2011-06-01  8:05             ` Russell King
2011-05-24  7:41   ` Artem Bityutskiy
2011-05-23 20:48 ` linux-next: Tree for May 23 (sound/soc/codecs) Randy Dunlap
2011-05-23 22:47   ` Mark Brown
2011-05-23 22:53     ` Randy Dunlap
2011-05-24  0:08       ` Mark Brown
2011-05-24  1:21         ` Randy Dunlap
2011-05-24  1:50           ` Mark Brown
2011-05-24  4:58             ` [PATCH/RFC] gpio: add GPIOF_ values regardless on kconfig settings Randy Dunlap
2011-05-24  5:23               ` Dmitry Artamonow
2011-05-24 19:44                 ` Randy Dunlap
2011-05-24  7:52               ` Mark Brown
2011-05-27  7:45                 ` [alsa-devel] " Grant Likely
2011-05-27 17:46                   ` [PATCH] " Randy Dunlap
2011-05-27 20:12                     ` Grant Likely
2011-06-03 17:04                       ` Grant Likely
2011-06-03 17:18                         ` Mark Brown
2011-06-03 17:42                           ` Grant Likely
2011-06-06  3:45                             ` Randy Dunlap
2011-06-14 16:12                               ` Randy Dunlap
2011-06-14 16:13                                 ` Grant Likely
2011-06-15  0:03                                   ` Randy Dunlap
2011-06-15  0:05                                   ` [PATCH 1/2] " Randy Dunlap
2011-06-16 14:37                                     ` Grant Likely
2011-06-15  0:06                                   ` [PATCH 2/2] gpio: include linux/gpio.h where needed Randy Dunlap
2011-06-15  0:34                                     ` Stephen Rothwell
2011-06-15 17:59                                       ` Randy Dunlap
2011-06-15 19:21                                         ` Grant Likely
2011-06-16 14:37                                     ` Grant Likely

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=1306222834.2785.53.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rmk@arm.linux.org.uk \
    --cc=sfr@canb.auug.org.au \
    /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).