All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Fix SPL build for non-ARM targets
Date: Wed, 9 Jan 2013 16:41:02 -0600	[thread overview]
Message-ID: <1357771262.18196.10@snotra> (raw)
In-Reply-To: <50EDEE6A.7080406@ti.com> (from trini@ti.com on Wed Jan  9 16:25:46 2013)

On 01/09/2013 04:25:46 PM, Tom Rini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 01/09/2013 05:06 PM, Scott Wood wrote:
> > BTW, the conflicting patch was
> > 5846b11e8810f0ecc15e78b383b7709b9b785580 ("am33xx_spl_bch: simple
> > SPL nand loader for AM33XX").  It's a NAND patch, in
> > drivers/mtd/nand specifically.  I don't see my ACK on it, and it
> > came in through the ti tree.
> 
> Putting on my u-boot-ti hat...
> 
> > If we were having custodians sign-off patches as they apply them,
> > you could tell from a glance that a patch is missing either
> > Acked-by or Signed-off-by from a relevant maintainer.
> 
> Yes, the series was posted Oct 30, and was minor updates to an
> existing SoC driver (omap_gpmc), some code for new related parts of
> the SoC (the ELM code, for offloading bch math) and a new SPL shim
> because there was no other way to get the read correct.  I merged it
> on or around Dec 10 and figured that since you hadn't spoken up in the
> intervening time, you didn't see anything worth commenting on.

I get a lot of e-mail.  Some of it gets missed.  If I haven't responded  
to something that directly touches drivers/mtd/nand within a reasonable  
time frame, please remind me rather than assume acquiscence.

Regardless, it's the manual merge that definitely needed review.

-Scott

      reply	other threads:[~2013-01-09 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 22:57 [U-Boot] [PATCH] Fix SPL build for non-ARM targets Albert ARIBAUD
2013-01-09 13:35 ` Tom Rini
2013-01-09 19:53 ` Scott Wood
2013-01-09 21:38   ` Tom Rini
2013-01-09 21:56     ` Scott Wood
2013-01-09 22:06     ` Scott Wood
2013-01-09 22:25       ` Tom Rini
2013-01-09 22:41         ` Scott Wood [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=1357771262.18196.10@snotra \
    --to=scottwood@freescale.com \
    --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 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.