linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Kao <alankao@andestech.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	kernel test robot <lkp@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	<kbuild-all@lists.01.org>,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	Greentime Hu <green.hu@gmail.com>,
	"Nick Hu" <nickhu@andestech.com>,
	Vincent Chen <deanbo422@gmail.com>, KC <kclin@andestech.com>,
	Masahiro Yamada <masahiroy@kernel.org>, <nickhu@sifive.com>,
	<nick.hu@sifive.com>
Subject: Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'
Date: Thu, 24 Feb 2022 17:56:04 +0800	[thread overview]
Message-ID: <YhdWNLUhk+x9RAzU@yamatobi.andestech.com> (raw)
In-Reply-To: <CAK8P3a0pr9_gHOieWf_gd4sFx7Z+urp420hMOBH+Hp5s-3-76g@mail.gmail.com>

Hi Arnd,

On Thu, Feb 24, 2022 at 09:38:30AM +0100, Arnd Bergmann wrote:
> On Thu, Feb 24, 2022 at 4:40 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Wed, 23 Feb 2022 19:12:45 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
> > > On 2/23/22 18:33, Steven Rostedt wrote:
> > > > On Wed, 23 Feb 2022 17:53:00 -0800
> > > > Randy Dunlap <rdunlap@infradead.org> wrote:
> > > >
> > > >> On 2/23/22 17:44, Randy Dunlap wrote:
> > > >>> Hi ktr, bouncing NDS32 maintainer, Andrew, Steven,
> > > >>>
> > > >>
> > > >> [now adding Andrew and Steven!]
> > > >
> > > > This needs to go via the NDS32 maintainers. If it's being ignored, then
> > > > we can consider the architecture as orphaned and start the process of
> > > > removal. ;-)
> > >
> > > Yes, it appears to be about that time...
> >
> > Hi Arnd,
> >
> > Just putting this on your "chopping block" radar.
> 
> Yes, that makes sense. I think nds32 was always going to be a
> short-lived architecture as Andestech was already in the process of
> moving to RISC-V before it was ever submitted upstream. I did
> hope that it would live a little longer, but it seems that everyone who
> ever worked on it in mainline has left andestech by now.
> 
> I'm guessing Nick's current email address based on his Linkedin page,
> maybe he can contact someone who is still there and able to
> take over.

I am in charge of this now.

> 
> I think nds32 is still in a better shape than a lot of the older
> architectures in mainline, and the CPU cores are still actively
> marketed for licensing. OTOH it only gets worse if nobody cares
> about the code, and users are probably already better off with
> one of the older longterm supported kernels. If we remove
> arch/nds32 before the next longterm release, that gives users
> stable updates until late 2026 using linux-5.10.y, which is
> probably sufficient.
> 
>         Arnd

All of our nds32 customers maintain their own kernel derived from
previous LTS versions.  Also, we (as the Linux team in Andes) now
dedicate our whole effort to RISC-V, so there is no longer need
to maintain arch/nds32.

We really appreciate your guidance and support.  Many thanks to
the community as well.

Alan


  reply	other threads:[~2022-02-24  9:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  0:04 [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off' kernel test robot
2022-02-24  1:44 ` Randy Dunlap
2022-02-24  1:53   ` Randy Dunlap
2022-02-24  2:33     ` Steven Rostedt
2022-02-24  2:38       ` Masahiro Yamada
2022-02-24  3:12       ` Randy Dunlap
2022-02-24  3:40         ` Steven Rostedt
2022-02-24  8:38           ` Arnd Bergmann
2022-02-24  9:56             ` Alan Kao [this message]
2022-02-24 11:57               ` Arnd Bergmann
2022-02-24 12:09                 ` 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=YhdWNLUhk+x9RAzU@yamatobi.andestech.com \
    --to=alankao@andestech.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=deanbo422@gmail.com \
    --cc=green.hu@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kclin@andestech.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=masahiroy@kernel.org \
    --cc=nick.hu@sifive.com \
    --cc=nickhu@andestech.com \
    --cc=nickhu@sifive.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.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).