From: Arnd Bergmann <arnd@arndb.de>
To: Alan Kao <alankao@andestech.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
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 12:57:28 +0100 [thread overview]
Message-ID: <CAK8P3a38QOei-NM-2Sy0evbhPav93Ch9gQVe1wHK_3P_+UFwcQ@mail.gmail.com> (raw)
In-Reply-To: <YhdWNLUhk+x9RAzU@yamatobi.andestech.com>
On Thu, Feb 24, 2022 at 10:56 AM Alan Kao <alankao@andestech.com> wrote:
> On Thu, Feb 24, 2022 at 09:38:30AM +0100, Arnd Bergmann wrote:
> >
> > 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.
Great, thanks for stepping up!
> 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.
Ok, sounds like it can indeed get phased out then. How would
you like to proceed here? Would you send a patch to remove
arch/nds32 and all the associated driver code that is no longer
used with your RISC-V based targets, or would you first update
the MAINTAINERS file to list yourself and pick a date for the
final removal?
Either way, feel free to send me patches to pick up in the
asm-generic tree.
Arnd
next prev parent reply other threads:[~2022-02-24 11: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
2022-02-24 11:57 ` Arnd Bergmann [this message]
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=CAK8P3a38QOei-NM-2Sy0evbhPav93Ch9gQVe1wHK_3P_+UFwcQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=alankao@andestech.com \
--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).