All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Jinyang He <hejinyang@loongson.cn>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	Wu Zhangjin <wuzhangjin@gmail.com>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Huacai Chen <chenhuacai@kernel.org>,
	Tiezhu Yang <yangtiezhu@loongson.cn>
Subject: Re: [PATCH 1/3] MIPS: ftrace: Fix N32 save registers
Date: Sat, 13 Feb 2021 16:17:50 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2102131609420.35623@angie.orcam.me.uk> (raw)
In-Reply-To: <83e49b6e-9c9d-407e-8ac1-f3fad63df915@www.fastmail.com>

On Mon, 1 Feb 2021, Jiaxun Yang wrote:

> > Thank you for your reply, and now I know. Before that, I saw the macro
> > from arch/mips/include/asm/regdef.h and thought it needed to be modified
> > here. But that seems have no sence.
> > Please ignore this patch.
> 
> I guess that's for uapi consideration.

 Nope, it's not under arch/mips/include/uapi/, but this is a common MIPS 
header used across many projects (see the copyright notices at the top 
going back to 1985), so there has been no sense to make Linux-specific 
changes to it just for the sake of it given that it works as it stands.  
Don't fix what ain't broke.  Don't make changes just because you can.

  Maciej

      reply	other threads:[~2021-02-13 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  8:14 [PATCH 1/3] MIPS: ftrace: Fix N32 save registers Jinyang He
2021-01-31  8:14 ` [PATCH 2/3] MIPS: ftrace: Combine ftrace_modify_code* into one function Jinyang He
2021-01-31  8:14 ` [PATCH 3/3] MIPS: ftrace: Add DYNAMIC_FTRACE_WITH_REGS support Jinyang He
2021-02-01 14:56   ` Steven Rostedt
2021-02-02 12:21     ` Jinyang He
     [not found] ` <b1a5eae4-2032-4ace-aa48-a21893e47528@www.fastmail.com>
2021-02-01  1:12   ` [PATCH 1/3] MIPS: ftrace: Fix N32 save registers Jinyang He
2021-02-01  4:03     ` Jiaxun Yang
2021-02-13 15:17       ` Maciej W. Rozycki [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=alpine.DEB.2.21.2102131609420.35623@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=chenhuacai@kernel.org \
    --cc=hejinyang@loongson.cn \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=wuzhangjin@gmail.com \
    --cc=yangtiezhu@loongson.cn \
    /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.