All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, soc@kernel.org,
	Arnd Bergmann <arnd@arndb.de>, Jun Nie <jun.nie@linaro.org>
Subject: Re: [PATCH 3/5] ARM: remove zte zx platform
Date: Fri, 29 Jan 2021 21:46:41 +0800	[thread overview]
Message-ID: <20210129134640.GG907@dragon> (raw)
In-Reply-To: <20210120124812.2800027-4-arnd@kernel.org>

On Wed, Jan 20, 2021 at 01:48:10PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> The ZTE ZX set-top-box SoC platform was added in 2015 by Jun Nie, with
> Baoyou Xie and Shawn Guo subsequently becoming maintainers after the
> addition of the 64-bit variant.
> 
> However, the only machines that were ever supported upstream are the
> reference designs, not actual set-top-box devices that would benefit
> from this support. All ZTE set-top-boxes from the past few years seem
> to be based on third-party SoCs. While there is very little information
> about zx296702 and zx296718 on the web, I found some references to other
> chips from the same family, such as zx296716 and zx296719, which were
> never submitted for upstream support. Finally, there is no support for
> the GPU on either of them, with the lima and panfrost device drivers
> having been added after work on the zx platform had stopped.
> 
> Shawn confirmed that he has not seen any interest in this platform for
> the past four years, and that it can be removed.
> 
> Thanks to Jun and Shawn for maintaining this platform over the past
> five years.
> 
> Cc: Jun Nie <jun.nie@linaro.org>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Acked-by: Shawn Guo <shawnguo@kernel.org>

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Jun Nie <jun.nie@linaro.org>,
	soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/5] ARM: remove zte zx platform
Date: Fri, 29 Jan 2021 21:46:41 +0800	[thread overview]
Message-ID: <20210129134640.GG907@dragon> (raw)
Message-ID: <20210129134641.h98-LwjdGThNoLwde8w4AFWKXm73YW9Ez5-nphN96Uk@z> (raw)
In-Reply-To: <20210120124812.2800027-4-arnd@kernel.org>

On Wed, Jan 20, 2021 at 01:48:10PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> The ZTE ZX set-top-box SoC platform was added in 2015 by Jun Nie, with
> Baoyou Xie and Shawn Guo subsequently becoming maintainers after the
> addition of the 64-bit variant.
> 
> However, the only machines that were ever supported upstream are the
> reference designs, not actual set-top-box devices that would benefit
> from this support. All ZTE set-top-boxes from the past few years seem
> to be based on third-party SoCs. While there is very little information
> about zx296702 and zx296718 on the web, I found some references to other
> chips from the same family, such as zx296716 and zx296719, which were
> never submitted for upstream support. Finally, there is no support for
> the GPU on either of them, with the lima and panfrost device drivers
> having been added after work on the zx platform had stopped.
> 
> Shawn confirmed that he has not seen any interest in this platform for
> the past four years, and that it can be removed.
> 
> Thanks to Jun and Shawn for maintaining this platform over the past
> five years.
> 
> Cc: Jun Nie <jun.nie@linaro.org>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Acked-by: Shawn Guo <shawnguo@kernel.org>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-01-29 13:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 12:48 [PATCH 0/5] ARM/c6x: remove orphaned platforms Arnd Bergmann
2021-01-20 12:48 ` Arnd Bergmann
2021-01-20 12:48 ` [PATCH 1/5] c6x: remove architecture Arnd Bergmann
2021-01-20 12:48   ` Arnd Bergmann
2021-01-21 15:44   ` Mark Salter
2021-01-21 15:44     ` Mark Salter
2021-01-21 15:44     ` Mark Salter
2021-02-03  7:52     ` Aurelien Jacquiot
2021-02-03  7:55     ` Aurelien Jacquiot
2021-02-03  7:55       ` Aurelien Jacquiot
2021-01-20 12:48 ` [PATCH 2/5] ARM: remove sirf prima2/atlas platforms Arnd Bergmann
2021-01-20 12:48   ` Arnd Bergmann
2021-01-20 12:48 ` [PATCH 3/5] ARM: remove zte zx platform Arnd Bergmann
2021-01-20 12:48   ` Arnd Bergmann
2021-01-29 13:46   ` Shawn Guo [this message]
2021-01-29 13:46     ` Shawn Guo
2021-08-04  8:51   ` Zenghui Yu
2021-08-04  8:51     ` Zenghui Yu
2021-01-20 12:48 ` [PATCH 4/5] ARM: remove tango platform Arnd Bergmann
2021-01-20 12:48   ` Arnd Bergmann
2021-01-21 13:47   ` Måns Rullgård
2021-01-21 13:47     ` Måns Rullgård
2021-01-20 12:48 ` [PATCH 5/5] ARM: remove u300 platform Arnd Bergmann
2021-01-20 12:48   ` Arnd Bergmann
2021-01-21  8:34   ` Linus Walleij
2021-01-21  8:34     ` Linus Walleij
2021-01-21  8:34     ` Linus Walleij
2021-01-21 10:02     ` Arnd Bergmann
2021-01-21 10:02       ` Arnd Bergmann

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=20210129134640.GG907@dragon \
    --to=shawnguo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=jun.nie@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.