public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd/nand: docg4: fix compiler warnings
Date: Thu, 27 Jun 2013 00:51:56 +0200	[thread overview]
Message-ID: <201306270051.56667.marex@denx.de> (raw)
In-Reply-To: <1372287031.8183.46@snotra>

Dear Scott Wood,

> On 06/26/2013 05:42:52 PM, Marek Vasut wrote:
> > Dear Scott Wood,
> > 
> > > On 06/26/2013 02:33:53 PM, Mike Dunn wrote:
> > > > Newer gcc versions warn about unused variables.  This patch
> > 
> > corrects
> > 
> > > > a few of
> > > > those warnings that popped up in a build for the palmtreo680
> > 
> > board.
> > 
> > > > Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
> > > > ---
> > > > 
> > > >  drivers/mtd/nand/docg4_spl.c | 15 +++++++--------
> > > >  1 file changed, 7 insertions(+), 8 deletions(-)
> > > 
> > > Applied to u-boot-nand-flash
> > > 
> > > -Scott
> > 
> > Ok, now I need Albert to pick the PXA PR and you will have to push
> > NAND PR after
> > the ARM PR is mainline. It's a bit complicated now.
> > 
> > The other way around would be that I pick both.
> > 
> > Albert?
> 
> Why would NAND need to wait until after ARM to request a pull?  If
> anything I'd think you'd want it the other way around so that the
> warnings are fixed by the time the board is merged.

Ok, the DoCG4 driver is already in, then it's all cool.

Best regards,
Marek Vasut

      reply	other threads:[~2013-06-26 22:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 19:33 [U-Boot] [PATCH] mtd/nand: docg4: fix compiler warnings Mike Dunn
2013-06-26 19:33 ` [U-Boot] [PATCH] usb: pxa27x_udc: " Mike Dunn
2013-06-26 21:20 ` [U-Boot] [PATCH] mtd/nand: docg4: " Scott Wood
2013-06-26 22:42   ` Marek Vasut
2013-06-26 22:50     ` Scott Wood
2013-06-26 22:51       ` Marek Vasut [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=201306270051.56667.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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