* [RFC] Sort out S5P SoCs support in mainline @ 2014-05-28 10:41 Kukjin Kim 2014-05-28 11:04 ` Arnd Bergmann 2014-05-28 11:08 ` Marek Szyprowski 0 siblings, 2 replies; 7+ messages in thread From: Kukjin Kim @ 2014-05-28 10:41 UTC (permalink / raw) To: linux-arm-kernel 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? Thanks, Kukjin ^ permalink raw reply [flat|nested] 7+ messages in thread
* [RFC] Sort out S5P SoCs support in mainline 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-28 11:08 ` Marek Szyprowski 1 sibling, 1 reply; 7+ messages in thread From: Arnd Bergmann @ 2014-05-28 11:04 UTC (permalink / raw) To: linux-arm-kernel 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* [RFC] Sort out S5P SoCs support in mainline 2014-05-28 11:04 ` Arnd Bergmann @ 2014-05-28 11:09 ` Tomasz Figa 2014-05-30 18:50 ` Kukjin Kim 0 siblings, 1 reply; 7+ messages in thread From: Tomasz Figa @ 2014-05-28 11:09 UTC (permalink / raw) To: linux-arm-kernel 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. Or better, if later somebody comes around who does need them, we can add them properly, using Device Tree and existing generic code. 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. Best regards, Tomasz ^ permalink raw reply [flat|nested] 7+ messages in thread
* [RFC] Sort out S5P SoCs support in mainline 2014-05-28 11:09 ` Tomasz Figa @ 2014-05-30 18:50 ` Kukjin Kim 2014-05-30 19:19 ` Tomasz Figa 0 siblings, 1 reply; 7+ messages in thread From: Kukjin Kim @ 2014-05-30 18:50 UTC (permalink / raw) To: linux-arm-kernel 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* [RFC] Sort out S5P SoCs support in mainline 2014-05-30 18:50 ` Kukjin Kim @ 2014-05-30 19:19 ` Tomasz Figa 0 siblings, 0 replies; 7+ messages in thread From: Tomasz Figa @ 2014-05-30 19:19 UTC (permalink / raw) To: linux-arm-kernel On 30.05.2014 20:50, Kukjin Kim wrote: > 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... Alright. I have a series to convert s5pv210 to DT-only waiting to be sent as soon as 3.16-rc1 is released, but if you remove those two first, I should be able to simplify several things, so I'll wait. Best regards, Tomasz ^ permalink raw reply [flat|nested] 7+ messages in thread
* [RFC] Sort out S5P SoCs support in mainline 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:08 ` Marek Szyprowski 2014-05-30 18:47 ` Kukjin Kim 1 sibling, 1 reply; 7+ messages in thread From: Marek Szyprowski @ 2014-05-28 11:08 UTC (permalink / raw) To: linux-arm-kernel Hello, On 2014-05-28 12:41, Kukjin Kim wrote: > 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'm okay with removing S5PC100. Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland ^ permalink raw reply [flat|nested] 7+ messages in thread
* [RFC] Sort out S5P SoCs support in mainline 2014-05-28 11:08 ` Marek Szyprowski @ 2014-05-30 18:47 ` Kukjin Kim 0 siblings, 0 replies; 7+ messages in thread From: Kukjin Kim @ 2014-05-30 18:47 UTC (permalink / raw) To: linux-arm-kernel On 05/28/14 20:08, Marek Szyprowski wrote: > Hello, > > On 2014-05-28 12:41, Kukjin Kim wrote: >> 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'm okay with removing S5PC100. > Thanks for your confirm on S5PC100. - Kukjin ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-05-30 19:19 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2014-05-30 19:19 ` Tomasz Figa 2014-05-28 11:08 ` Marek Szyprowski 2014-05-30 18:47 ` Kukjin Kim
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).