From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Sort out S5P SoCs support in mainline
Date: Sat, 31 May 2014 03:50:13 +0900 [thread overview]
Message-ID: <5388D2E5.5080006@samsung.com> (raw)
In-Reply-To: <5385C3CC.6010509@gmail.com>
On 05/28/14 20:09, Tomasz Figa wrote:
> On 28.05.2014 13:04, Arnd Bergmann wrote:
>> 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.
Yeah, agreed.
>
> Or better, if later somebody comes around who does need them, we can add
> them properly, using Device Tree and existing generic code.
>
Of course.
> Anyway, for removal of both s5p64x0 and s5pc100:
>
> Acked-by: Tomasz Figa<t.figa@samsung.com>
>
> Actually I have played a bit with the code to see how much can be
> removed and ended up with following branch:
>
> https://github.com/tom3q/linux.git v3.17-cleanup
>
> Feel free to do _whatever_ you want with patches there.
>
OK, thanks.
Let me remove them from mainline when 3.16-rc1 is released...
- Kukjin
next prev parent reply other threads:[~2014-05-30 18:50 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
2014-05-28 11:09 ` Tomasz Figa
2014-05-30 18:50 ` Kukjin Kim [this message]
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=5388D2E5.5080006@samsung.com \
--to=kgene.kim@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).