From: Vineet Gupta <vgupta@synopsys.com>
To: Yury Norov <ynorov@caviumnetworks.com>,
Arnd Bergmann <arnd@arndb.de>,
James Hogan <james.hogan@imgtec.com>,
"linux-arch@vger.kernel.or" <linux-arch@vger.kernel.or>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Mark Salter <msalter@redhat.com>,
Aurelien Jacquiot <a-jacquiot@ti.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Richard Kuo <rkuo@codeaurora.org>,
Ley Foon Tan <lftan@altera.com>, Jonas Bonn <jonas@southpole.se>,
Chen Liqin <liqin.linux@gmail.com>,
Lennox Wu <lennox.wu@gmail.com>,
Chris Metcalf <cmetcalf@mellanox.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Andrew Pinski <Andrew.Pinski@cavium.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] asm-generic: Drop getrlimit and setrlimit syscalls from default list
Date: Sun, 23 Oct 2016 13:57:27 -0700 [thread overview]
Message-ID: <4e1a4e68-5c84-ce9d-73df-b7da312cc884@synopsys.com> (raw)
In-Reply-To: <1477138444-14993-1-git-send-email-ynorov@caviumnetworks.com>
On 10/22/2016 05:14 AM, Yury Norov wrote:
> The newer prlimit64 syscall provides all the functionality provided by
> the getrlimit and setrlimit syscalls and adds the pid of target process,
> so future architectures won't need to include getrlimit and setrlimit.
>
> Therefore drop getrlimit and setrlimit syscalls from the generic syscall
> list unless __ARCH_WANT_SET_GET_RLIMIT is defined by the architecture's
> unistd.h prior to including asm-generic/unistd.h, and adjust all
> architectures using the generic syscall list to define it so that no
> in-tree architectures are affected.
>
> Cc: Vineet Gupta <vgupta@synopsys.com>
Acked-by: Vineet Gupta <vgupta@synopsys.com> #arch/arc bits
Thx,
-Vineet
next prev parent reply other threads:[~2016-10-23 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 12:14 [PATCH] asm-generic: Drop getrlimit and setrlimit syscalls from default list Yury Norov
2016-10-23 20:57 ` Vineet Gupta [this message]
[not found] ` <1477138444-14993-1-git-send-email-ynorov-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-10-24 9:09 ` James Hogan
[not found] ` <20161024090931.GR7370-4bYivNCBEGTR3KXKvIWQxtm+Uo4AYnCiHZ5vskTnxNA@public.gmane.org>
2016-10-25 0:47 ` Ley Foon Tan
[not found] ` <CAFiDJ59PdOiqiF8wFVFrkB4k0B6S5cTGVQPUpdjZ=83iv7GQag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-25 12:51 ` Stafford Horne
2016-10-29 21:02 ` Arnd Bergmann
2016-10-29 21:45 ` Yury Norov
2016-10-29 21:52 ` Arnd Bergmann
2016-10-29 23:06 ` James Hogan
2016-10-29 21:54 ` Arnd Bergmann
2016-10-29 22:05 ` Yury Norov
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=4e1a4e68-5c84-ce9d-73df-b7da312cc884@synopsys.com \
--to=vgupta@synopsys.com \
--cc=Andrew.Pinski@cavium.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=a-jacquiot@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cmetcalf@mellanox.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=james.hogan@imgtec.com \
--cc=jonas@southpole.se \
--cc=lennox.wu@gmail.com \
--cc=lftan@altera.com \
--cc=linux-arch@vger.kernel.or \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=liqin.linux@gmail.com \
--cc=msalter@redhat.com \
--cc=rkuo@codeaurora.org \
--cc=will.deacon@arm.com \
--cc=ynorov@caviumnetworks.com \
--cc=ysato@users.sourceforge.jp \
/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