From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Sort out S5P SoCs support in mainline
Date: Wed, 28 May 2014 13:04:02 +0200 [thread overview]
Message-ID: <13875033.1X6R9lksgc@wuerfel> (raw)
In-Reply-To: <021f01cf7a61$69853e30$3c8fba90$@samsung.com>
On Wednesday 28 May 2014 19:41:41 Kukjin Kim wrote:
> Hi all,
>
> I'm wondering who need to support following SoCs/boards in mainline.
>
> * S5P64X0/SMDK6440 and SMDK6450
> * S5PC100/SMDKC100
>
> If nobody is using them, how about to remove them from mainline?
I talked about this with Tomasz Figa before, he also thinks they can be removed.
I don't see any reason to keep them myself, and will apply a patch to remove
them. Of course, if later somebody comes around who does need them, we can
revert the patch to bring them back.
Arnd
next prev parent reply other threads:[~2014-05-28 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 10:41 [RFC] Sort out S5P SoCs support in mainline Kukjin Kim
2014-05-28 11:04 ` Arnd Bergmann [this message]
2014-05-28 11:09 ` Tomasz Figa
2014-05-30 18:50 ` Kukjin Kim
2014-05-30 19:19 ` Tomasz Figa
2014-05-28 11:08 ` Marek Szyprowski
2014-05-30 18:47 ` Kukjin Kim
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=13875033.1X6R9lksgc@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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