[linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[kernel test robot]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   196d330d7fb1e7cc0d85641c89ce4602cb36f12e
commit: 36b9b19753937a6fe0e591b518d46a1f2efae679 [70/7526] nds32: add a Kconfig symbol for LOCKDEP_SUPPORT
config: nds32-randconfig-r023-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240745.3HwmSv5A-lkp@intel.com/config)
compiler: nds32le-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=36b9b19753937a6fe0e591b518d46a1f2efae679
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 36b9b19753937a6fe0e591b518d46a1f2efae679
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   nds32le-linux-ld: arch/nds32/kernel/ex-entry.o: in function `fucop_ctl_done':
>> (.text+0x12a): undefined reference to `__trace_hardirqs_off'
   (.text+0x12a): relocation truncated to fit: R_NDS32_25_PCREL_RELA against undefined symbol `__trace_hardirqs_off'
   nds32le-linux-ld: arch/nds32/kernel/ex-exit.o: in function `no_work_pending':
   (.text+0xea): undefined reference to `__trace_hardirqs_off'
   nds32le-linux-ld: (.text+0xee): undefined reference to `__trace_hardirqs_off'
>> nds32le-linux-ld: (.text+0xf2): undefined reference to `__trace_hardirqs_on'
   nds32le-linux-ld: (.text+0xf6): undefined reference to `__trace_hardirqs_on'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Randy Dunlap]

Hi ktr, bouncing NDS32 maintainer, Andrew, Steven,


On 2/23/22 16:04, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   196d330d7fb1e7cc0d85641c89ce4602cb36f12e
> commit: 36b9b19753937a6fe0e591b518d46a1f2efae679 [70/7526] nds32: add a Kconfig symbol for LOCKDEP_SUPPORT
> config: nds32-randconfig-r023-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240745.3HwmSv5A-lkp@intel.com/config)
> compiler: nds32le-linux-gcc (GCC) 11.2.0
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=36b9b19753937a6fe0e591b518d46a1f2efae679
>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>         git fetch --no-tags linux-next master
>         git checkout 36b9b19753937a6fe0e591b518d46a1f2efae679
>         # save the config file to linux build tree
>         mkdir build_dir
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    nds32le-linux-ld: arch/nds32/kernel/ex-entry.o: in function `fucop_ctl_done':
>>> (.text+0x12a): undefined reference to `__trace_hardirqs_off'
>    (.text+0x12a): relocation truncated to fit: R_NDS32_25_PCREL_RELA against undefined symbol `__trace_hardirqs_off'
>    nds32le-linux-ld: arch/nds32/kernel/ex-exit.o: in function `no_work_pending':
>    (.text+0xea): undefined reference to `__trace_hardirqs_off'
>    nds32le-linux-ld: (.text+0xee): undefined reference to `__trace_hardirqs_off'
>>> nds32le-linux-ld: (.text+0xf2): undefined reference to `__trace_hardirqs_on'
>    nds32le-linux-ld: (.text+0xf6): undefined reference to `__trace_hardirqs_on'

I have posted v1 and v2 patches for this problem (as well as other NDS32 patches),
but the NDS32 maintainer seems to have disappeared.

v1:  https://lore.kernel.org/lkml/20210928052657.20909-1-rdunlap@infradead.org/
v2:  https://lore.kernel.org/lkml/20220217191347.13480-1-rdunlap@infradead.org/


Any takers?

thanks.
-- 
~Randy

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Randy Dunlap]

[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]

Hi ktr, bouncing NDS32 maintainer, Andrew, Steven,


On 2/23/22 16:04, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   196d330d7fb1e7cc0d85641c89ce4602cb36f12e
> commit: 36b9b19753937a6fe0e591b518d46a1f2efae679 [70/7526] nds32: add a Kconfig symbol for LOCKDEP_SUPPORT
> config: nds32-randconfig-r023-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240745.3HwmSv5A-lkp(a)intel.com/config)
> compiler: nds32le-linux-gcc (GCC) 11.2.0
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=36b9b19753937a6fe0e591b518d46a1f2efae679
>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>         git fetch --no-tags linux-next master
>         git checkout 36b9b19753937a6fe0e591b518d46a1f2efae679
>         # save the config file to linux build tree
>         mkdir build_dir
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    nds32le-linux-ld: arch/nds32/kernel/ex-entry.o: in function `fucop_ctl_done':
>>> (.text+0x12a): undefined reference to `__trace_hardirqs_off'
>    (.text+0x12a): relocation truncated to fit: R_NDS32_25_PCREL_RELA against undefined symbol `__trace_hardirqs_off'
>    nds32le-linux-ld: arch/nds32/kernel/ex-exit.o: in function `no_work_pending':
>    (.text+0xea): undefined reference to `__trace_hardirqs_off'
>    nds32le-linux-ld: (.text+0xee): undefined reference to `__trace_hardirqs_off'
>>> nds32le-linux-ld: (.text+0xf2): undefined reference to `__trace_hardirqs_on'
>    nds32le-linux-ld: (.text+0xf6): undefined reference to `__trace_hardirqs_on'

I have posted v1 and v2 patches for this problem (as well as other NDS32 patches),
but the NDS32 maintainer seems to have disappeared.

v1:  https://lore.kernel.org/lkml/20210928052657.20909-1-rdunlap(a)infradead.org/
v2:  https://lore.kernel.org/lkml/20220217191347.13480-1-rdunlap(a)infradead.org/


Any takers?

thanks.
-- 
~Randy

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Randy Dunlap]

On 2/23/22 17:44, Randy Dunlap wrote:
> Hi ktr, bouncing NDS32 maintainer, Andrew, Steven,
> 

[now adding Andrew and Steven!]

> 
> On 2/23/22 16:04, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   196d330d7fb1e7cc0d85641c89ce4602cb36f12e
>> commit: 36b9b19753937a6fe0e591b518d46a1f2efae679 [70/7526] nds32: add a Kconfig symbol for LOCKDEP_SUPPORT
>> config: nds32-randconfig-r023-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240745.3HwmSv5A-lkp@intel.com/config)
>> compiler: nds32le-linux-gcc (GCC) 11.2.0
>> reproduce (this is a W=1 build):
>>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>         chmod +x ~/bin/make.cross
>>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=36b9b19753937a6fe0e591b518d46a1f2efae679
>>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>         git fetch --no-tags linux-next master
>>         git checkout 36b9b19753937a6fe0e591b518d46a1f2efae679
>>         # save the config file to linux build tree
>>         mkdir build_dir
>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 SHELL=/bin/bash
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>    nds32le-linux-ld: arch/nds32/kernel/ex-entry.o: in function `fucop_ctl_done':
>>>> (.text+0x12a): undefined reference to `__trace_hardirqs_off'
>>    (.text+0x12a): relocation truncated to fit: R_NDS32_25_PCREL_RELA against undefined symbol `__trace_hardirqs_off'
>>    nds32le-linux-ld: arch/nds32/kernel/ex-exit.o: in function `no_work_pending':
>>    (.text+0xea): undefined reference to `__trace_hardirqs_off'
>>    nds32le-linux-ld: (.text+0xee): undefined reference to `__trace_hardirqs_off'
>>>> nds32le-linux-ld: (.text+0xf2): undefined reference to `__trace_hardirqs_on'
>>    nds32le-linux-ld: (.text+0xf6): undefined reference to `__trace_hardirqs_on'
> 
> I have posted v1 and v2 patches for this problem (as well as other NDS32 patches),
> but the NDS32 maintainer seems to have disappeared.
> 
> v1:  https://lore.kernel.org/lkml/20210928052657.20909-1-rdunlap@infradead.org/
> v2:  https://lore.kernel.org/lkml/20220217191347.13480-1-rdunlap@infradead.org/
> 
> 
> Any takers?
> 
> thanks.

-- 
~Randy

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Randy Dunlap]

[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]



On 2/23/22 17:44, Randy Dunlap wrote:
> Hi ktr, bouncing NDS32 maintainer, Andrew, Steven,
> 

[now adding Andrew and Steven!]

> 
> On 2/23/22 16:04, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   196d330d7fb1e7cc0d85641c89ce4602cb36f12e
>> commit: 36b9b19753937a6fe0e591b518d46a1f2efae679 [70/7526] nds32: add a Kconfig symbol for LOCKDEP_SUPPORT
>> config: nds32-randconfig-r023-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240745.3HwmSv5A-lkp(a)intel.com/config)
>> compiler: nds32le-linux-gcc (GCC) 11.2.0
>> reproduce (this is a W=1 build):
>>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>         chmod +x ~/bin/make.cross
>>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=36b9b19753937a6fe0e591b518d46a1f2efae679
>>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>         git fetch --no-tags linux-next master
>>         git checkout 36b9b19753937a6fe0e591b518d46a1f2efae679
>>         # save the config file to linux build tree
>>         mkdir build_dir
>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 SHELL=/bin/bash
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>    nds32le-linux-ld: arch/nds32/kernel/ex-entry.o: in function `fucop_ctl_done':
>>>> (.text+0x12a): undefined reference to `__trace_hardirqs_off'
>>    (.text+0x12a): relocation truncated to fit: R_NDS32_25_PCREL_RELA against undefined symbol `__trace_hardirqs_off'
>>    nds32le-linux-ld: arch/nds32/kernel/ex-exit.o: in function `no_work_pending':
>>    (.text+0xea): undefined reference to `__trace_hardirqs_off'
>>    nds32le-linux-ld: (.text+0xee): undefined reference to `__trace_hardirqs_off'
>>>> nds32le-linux-ld: (.text+0xf2): undefined reference to `__trace_hardirqs_on'
>>    nds32le-linux-ld: (.text+0xf6): undefined reference to `__trace_hardirqs_on'
> 
> I have posted v1 and v2 patches for this problem (as well as other NDS32 patches),
> but the NDS32 maintainer seems to have disappeared.
> 
> v1:  https://lore.kernel.org/lkml/20210928052657.20909-1-rdunlap(a)infradead.org/
> v2:  https://lore.kernel.org/lkml/20220217191347.13480-1-rdunlap(a)infradead.org/
> 
> 
> Any takers?
> 
> thanks.

-- 
~Randy

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Steven Rostedt]

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. ;-)

Masahiro was the last to touch this arch with a "nds32:" subject,
perhaps he cares?

-- Steve

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Steven Rostedt]

[-- Attachment #1: Type: text/plain, Size: 485 bytes --]

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. ;-)

Masahiro was the last to touch this arch with a "nds32:" subject,
perhaps he cares?

-- Steve

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Masahiro Yamada]

On Thu, Feb 24, 2022 at 11:33 AM Steven Rostedt <rostedt@goodmis.org> 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. ;-)
>
> Masahiro was the last to touch this arch with a "nds32:" subject,
> perhaps he cares?

Not really.

I just modified some Makefiles under arch/nds32/.
I do not know much about this architecture.




>
> -- Steve



-- 
Best Regards
Masahiro Yamada

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Masahiro Yamada]

[-- Attachment #1: Type: text/plain, Size: 755 bytes --]

On Thu, Feb 24, 2022 at 11:33 AM Steven Rostedt <rostedt@goodmis.org> 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. ;-)
>
> Masahiro was the last to touch this arch with a "nds32:" subject,
> perhaps he cares?

Not really.

I just modified some Makefiles under arch/nds32/.
I do not know much about this architecture.




>
> -- Steve



-- 
Best Regards
Masahiro Yamada

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Randy Dunlap]

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...

> Masahiro was the last to touch this arch with a "nds32:" subject,
> perhaps he cares?


-- 
~Randy

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Randy Dunlap]

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]



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...

> Masahiro was the last to touch this arch with a "nds32:" subject,
> perhaps he cares?


-- 
~Randy

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Steven Rostedt]

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.

-- Steve


> 
> > Masahiro was the last to touch this arch with a "nds32:" subject,
> > perhaps he cares?
> 
> 

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Steven Rostedt]

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

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.

-- Steve


> 
> > Masahiro was the last to touch this arch with a "nds32:" subject,
> > perhaps he cares?
> 
> 

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Arnd Bergmann]

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 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

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Arnd Bergmann]

[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]

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 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

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Alan Kao]

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

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Alan Kao]

[-- Attachment #1: Type: text/plain, Size: 2245 bytes --]

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

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Arnd Bergmann]

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

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Arnd Bergmann]

[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]

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

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Arnd Bergmann]

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

Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'

[Arnd Bergmann]

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

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(a)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