From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] sparc: consolidate CONFIG_{LEON, LEON2, LEON3} definition
Date: Fri, 28 Mar 2014 11:42:40 -0400 [thread overview]
Message-ID: <20140328154240.GP16360@bill-the-cat> (raw)
In-Reply-To: <20140328113449.DB38.AA925319@jp.panasonic.com>
On Fri, Mar 28, 2014 at 11:34:49AM +0900, Masahiro Yamada wrote:
> Hi Tom,
>
> On Thu, 27 Mar 2014 13:00:19 -0400
> Tom Rini <trini@ti.com> wrote:
>
> > On Thu, Mar 13, 2014 at 07:48:57PM +0900, Masahiro Yamada wrote:
> >
> > > CONFIG_LEON is already defined in
> > > arch/sparc/cpu/{leon2,leon3}/config.mk.
> > > Remove the redundant definition in board header files.
> > >
> > > All leon3 boards define CONFIG_LEON3 in board header files.
> > > Move the definition to arch/sparc/cpu/leon3/config.mk.
> > >
> > > CONFIG_LEON2 can be move to arch/sparc/cpu/leon2/config.mk
> > > as well.
> > >
> > > Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> > > Cc: Daniel Hellstrom <daniel@gaisler.com>
> >
> > Applied to u-boot/next, thanks!
>
> Why did today's updates go to u-boot/next, not u-boot/master?
I'm trying to slow down what's pulled in and since sparc doesn't build
for me today (unrelated to Kbuild), I figured I'd hold this one off for
the next release, while I was adding other stuff to /next anyhow.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140328/62a1bff5/attachment.pgp>
next prev parent reply other threads:[~2014-03-28 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 10:48 [U-Boot] [PATCH] sparc: consolidate CONFIG_{LEON, LEON2, LEON3} definition Masahiro Yamada
2014-03-27 17:00 ` [U-Boot] " Tom Rini
2014-03-28 2:34 ` Masahiro Yamada
2014-03-28 15:42 ` Tom Rini [this message]
2014-03-31 2:12 ` Masahiro Yamada
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=20140328154240.GP16360@bill-the-cat \
--to=trini@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox