From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Update and cut down mach types
Date: Sat, 23 Apr 2011 16:47:40 +0200 [thread overview]
Message-ID: <4DB2E68C.6050508@aribaud.net> (raw)
In-Reply-To: <1303182758-10449-1-git-send-email-s-paulraj@ti.com>
Hi Sandeep,
Le 19/04/2011 05:12, s-paulraj at ti.com a ?crit :
> From: Sandeep Paulraj<s-paulraj@ti.com>
>
> This commit updates u-boot with what is present in the
> kernel.
>
> As many entries have never been submitted to mainline, there's no point
> them existing in this file. So remove the entries which aren't relevant
> for mainline.
>
>
> Signed-off-by: Sandeep Paulraj<s-paulraj@ti.com>
> ---
> arch/arm/include/asm/mach-types.h |31044 ++-----------------------------------
> 1 files changed, 1079 insertions(+), 29965 deletions(-)
NAK at least for this release: it would break several boards including
one for which support has just been added.
I understand the desire to remove what is quite dead code, but then we
need to agree on a clean way to properly handle those boards that Linux
does not support.
Amicalement,
--
Albert.
parent reply other threads:[~2011-04-23 14:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1303182758-10449-1-git-send-email-s-paulraj@ti.com>]
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=4DB2E68C.6050508@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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