All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: 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>,
	Alan Kao <alankao@andestech.com>, KC <kclin@andestech.com>
Subject: Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'
Date: Thu, 24 Feb 2022 11:38:30 +0900	[thread overview]
Message-ID: <CAK7LNASyehG2q49NUkEyXf1u+54MzzMpmjoVc_yq-duqDHZ4fw@mail.gmail.com> (raw)
In-Reply-To: <20220223213316.75ee31f8@rorschach.local.home>

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


WARNING: multiple messages have this Message-ID (diff)
From: Masahiro Yamada <masahiroy@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 70/7526] undefined reference to `__trace_hardirqs_off'
Date: Thu, 24 Feb 2022 11:38:30 +0900	[thread overview]
Message-ID: <CAK7LNASyehG2q49NUkEyXf1u+54MzzMpmjoVc_yq-duqDHZ4fw@mail.gmail.com> (raw)
In-Reply-To: <20220223213316.75ee31f8@rorschach.local.home>

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

  reply	other threads:[~2022-02-24  2:39 UTC|newest]

Thread overview: 21+ 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:44   ` Randy Dunlap
2022-02-24  1:53   ` Randy Dunlap
2022-02-24  1:53     ` Randy Dunlap
2022-02-24  2:33     ` Steven Rostedt
2022-02-24  2:33       ` Steven Rostedt
2022-02-24  2:38       ` Masahiro Yamada [this message]
2022-02-24  2:38         ` Masahiro Yamada
2022-02-24  3:12       ` Randy Dunlap
2022-02-24  3:12         ` Randy Dunlap
2022-02-24  3:40         ` Steven Rostedt
2022-02-24  3:40           ` Steven Rostedt
2022-02-24  8:38           ` Arnd Bergmann
2022-02-24  8:38             ` Arnd Bergmann
2022-02-24  9:56             ` Alan Kao
2022-02-24  9:56               ` Alan Kao
2022-02-24 11:57               ` Arnd Bergmann
2022-02-24 11:57                 ` Arnd Bergmann
2022-02-24 12:09                 ` 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=CAK7LNASyehG2q49NUkEyXf1u+54MzzMpmjoVc_yq-duqDHZ4fw@mail.gmail.com \
    --to=masahiroy@kernel.org \
    --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=nickhu@andestech.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 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.