public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alexander Lobakin <alobakin@pm.me>,
	Andrew Morton <akpm@linux-foundation.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Michal Simek <michal.simek@xilinx.com>,
	Stefan Asserhall <stefan.asserhall@xilinx.com>
Subject: Re: [PATCH 2/2] mips: syscalls: switch to generic syscallhdr.sh
Date: Wed, 10 Mar 2021 16:07:27 +0100	[thread overview]
Message-ID: <20210310150727.GB12960@alpha.franken.de> (raw)
In-Reply-To: <20210301144825.357922-2-masahiroy@kernel.org>

On Mon, Mar 01, 2021 at 11:48:25PM +0900, Masahiro Yamada wrote:
> Many architectures duplicate similar shell scripts.
> 
> This commit converts mips to use scripts/syscallhdr.sh.
> 
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> 
>  arch/mips/kernel/syscalls/Makefile      | 10 ++-----
>  arch/mips/kernel/syscalls/syscallhdr.sh | 36 -------------------------
>  2 files changed, 2 insertions(+), 44 deletions(-)
>  delete mode 100644 arch/mips/kernel/syscalls/syscallhdr.sh

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2021-03-10 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 14:48 [PATCH 1/2] mips: syscalls: switch to generic syscalltbl.sh Masahiro Yamada
2021-03-01 14:48 ` [PATCH 2/2] mips: syscalls: switch to generic syscallhdr.sh Masahiro Yamada
2021-03-10 15:07   ` Thomas Bogendoerfer [this message]
2021-03-10 15:07 ` [PATCH 1/2] mips: syscalls: switch to generic syscalltbl.sh Thomas Bogendoerfer

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=20210310150727.GB12960@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=akpm@linux-foundation.org \
    --cc=alobakin@pm.me \
    --cc=geert@linux-m68k.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=stefan.asserhall@xilinx.com \
    /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