From: Arnd Bergmann <arnd@arndb.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Alan Kao <alankao@andestech.com>,
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 13:09:46 +0100 [thread overview]
Message-ID: <CAK8P3a00PGMD25v5+Rnt0coNcg=YQV3gSrWNwqgU-ASp858cfg@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a38QOei-NM-2Sy0evbhPav93Ch9gQVe1wHK_3P_+UFwcQ@mail.gmail.com>
On Thu, Feb 24, 2022 at 12:57 PM Arnd Bergmann <arnd@arndb.de> wrote:
> 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.
On a related note, you may want to pick up
https://lore.kernel.org/lkml/20220216131332.1489939-4-arnd@kernel.org/
into any 4.19 (or higher) tree that is still getting updated. I'm leaving this
in my series for 5.18 regardless of what happens to arch/nds32 as a whole,
so it should also make it into all the longerm backports, but this one would
also be a good one for you to pick up without waiting for a stable kernel
update.
Arnd
prev parent reply other threads:[~2022-02-24 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 0:04 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
2022-02-24 12:09 ` Arnd Bergmann [this message]
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='CAK8P3a00PGMD25v5+Rnt0coNcg=YQV3gSrWNwqgU-ASp858cfg@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