From: Richard Cochran <richardcochran@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
David Gstir <david@sigma-star.at>
Subject: Re: [PATCH] Implement leftpad syscall
Date: Fri, 1 Apr 2016 08:56:39 +0200 [thread overview]
Message-ID: <20160401065639.GA28596@localhost.localdomain> (raw)
In-Reply-To: <1459463613-32473-2-git-send-email-richard@nod.at>
On Fri, Apr 01, 2016 at 12:33:32AM +0200, Richard Weinberger wrote:
> From: David Gstir <david@sigma-star.at>
>
> Implement the leftpad() system call such that userspace,
> especially node.js applications, can in the near future directly
> use it and no longer depend on fragile npm packages.
>
> Signed-off-by: David Gstir <david@sigma-star.at>
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
> arch/x86/entry/syscalls/syscall_64.tbl | 1 +
> include/linux/syscalls.h | 1 +
> kernel/sys.c | 35 ++++++++++++++++++++++++++++++++++
> kernel/sys_ni.c | 1 +
> 4 files changed, 38 insertions(+)
This is okay as far as it goes, but you need to add the other archs
and put the relevant maintainers onto CC.
Thanks,
Richard
next prev parent reply other threads:[~2016-04-01 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 22:33 New syscall: leftpad() Richard Weinberger
2016-03-31 22:33 ` [PATCH] Implement leftpad syscall Richard Weinberger
2016-03-31 22:46 ` Michael Kerrisk (man-pages)
2016-03-31 23:09 ` Greg KH
2016-04-01 1:33 ` Frederic Weisbecker
2016-04-01 3:22 ` kbuild test robot
2016-04-01 6:56 ` Richard Cochran [this message]
2016-04-01 7:14 ` Scotty Bauer
2016-03-31 22:33 ` [PATCH] leftpad.2: Document new syscall Richard Weinberger
2016-04-08 18:10 ` Heinrich Schuchardt
2016-04-09 14:12 ` Richard Weinberger
2016-03-31 23:36 ` New syscall: leftpad() Randy Dunlap
2016-04-01 8:06 ` Richard Weinberger
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=20160401065639.GA28596@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=david@sigma-star.at \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
/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