From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/4] arm: Remove smdk2410 board
Date: Sat, 26 Nov 2016 09:07:09 -0500 [thread overview]
Message-ID: <20161126140709.GQ2546@bill-the-cat> (raw)
In-Reply-To: <CAD6G_RR_uGHv1aKLN3fex6bSKOg57K6vFgGVssXW5t5YL0DbHw@mail.gmail.com>
On Sat, Nov 26, 2016 at 07:30:36PM +0530, Jagan Teki wrote:
> On Sat, Nov 26, 2016 at 7:14 PM, Tom Rini <trini@konsulko.com> wrote:
> > On Sat, Nov 26, 2016 at 07:03:33PM +0530, Jagan Teki wrote:
> >> On Wed, Nov 23, 2016 at 6:31 PM, Simon Glass <sjg@chromium.org> wrote:
> >> > This board has not been converted to DM_SERIAL by the deadline.
> >> > Remove it.
> >> >
> >> > Signed-off-by: Simon Glass <sjg@chromium.org>
> >> > ---
> >>
> >> < snip>
> >>
> >> > CONFIG_ARCH_SHARK
> >> > -CONFIG_ARCH_SMDK2410
> >>
> >> Code relate to this still there in arch/arm/include/asm/mach-types.h,
> >
> > That's a file we sync(ed) from the kernel and should leave alone, imho.
>
> I always think that the code related to the CONFIG_* which are listed
> in config_whitelist.txt should be dropped as there is no usage on the
> tree.
Yes, but that's a special case of a file that we should just not touch.
I will however accept the argument that we should re-sync the file with
a generated copy from v4.8 for example but only take the MACH_TYPE_xxx
part and remove all of the machine_is_xxx parts of the file.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161126/3326857c/attachment.sig>
next prev parent reply other threads:[~2016-11-26 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 13:01 [U-Boot] [PATCH v2 0/4] dm: Update on serial driver progress Simon Glass
2016-11-23 13:01 ` [U-Boot] [PATCH v2 1/4] serial: Update docs to indicate mcfuart supports DM_SERIAL Simon Glass
2016-12-04 23:27 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-11-23 13:01 ` [U-Boot] [PATCH v2 2/4] arm: Remove smdk2410 board Simon Glass
2016-11-26 7:24 ` David Müller (ELSOFT AG)
2016-11-26 13:33 ` Jagan Teki
2016-11-26 13:44 ` Tom Rini
2016-11-26 14:00 ` Jagan Teki
2016-11-26 14:07 ` Tom Rini [this message]
2016-12-04 23:29 ` [U-Boot] [U-Boot,v2,2/4] " Tom Rini
2016-11-23 13:01 ` [U-Boot] [PATCH v2 3/4] arm: Remove VCMA9 board Simon Glass
2016-11-26 7:25 ` David Müller (ELSOFT AG)
2016-11-26 13:37 ` Jagan Teki
2016-12-04 23:30 ` [U-Boot] [U-Boot,v2,3/4] " Tom Rini
2016-11-23 13:01 ` [U-Boot] [PATCH v2 4/4] serial: Drop the s3c24x0 serial driver Simon Glass
2016-11-26 7:25 ` David Müller (ELSOFT AG)
2016-11-26 13:39 ` Jagan Teki
2016-12-04 23:31 ` [U-Boot] [U-Boot, v2, " Tom Rini
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=20161126140709.GQ2546@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