From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Add and select CONFIG_ARMV7
Date: Wed, 9 Dec 2015 21:21:46 -0500 [thread overview]
Message-ID: <20151210022146.GQ667@bill-the-cat> (raw)
In-Reply-To: <20151208162049.2D15F383F2E@gemini.denx.de>
On Tue, Dec 08, 2015 at 05:20:49PM +0100, Wolfgang Denk wrote:
> Dear Marek,
>
> In message <201512081439.50797.marex@denx.de> you wrote:
> >
> > Please ignore, after discussing this on IRC, we decided on doing
> > s/CONFIG_ARMV7/CONFIG_CPU_V7/g instead.
>
> As IRC si (to the best or my knowledge?) not logged anywhere, I would
> like to hear the rationale for this decision.
We're following Linux kernel convention and using the existing CPU_V7
option we have.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151209/097a1ed3/attachment.sig>
prev parent reply other threads:[~2015-12-10 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 13:21 [U-Boot] [PATCH] arm: Add and select CONFIG_ARMV7 Marek Vasut
2015-12-08 13:39 ` Marek Vasut
2015-12-08 16:20 ` Wolfgang Denk
2015-12-10 2:21 ` Tom Rini [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=20151210022146.GQ667@bill-the-cat \
--to=trini@konsulko.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