public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use __kernel_long_t/__kernel_ulong_t in <linux/resource.h>
Date: Thu, 26 Dec 2013 02:03:48 -0800	[thread overview]
Message-ID: <20131226100348.GA7751@infradead.org> (raw)
In-Reply-To: <20131225145447.GA18146@gmail.com>

On Wed, Dec 25, 2013 at 06:54:47AM -0800, H.J. Lu wrote:
> Both x32 and x86-64 use the same struct rusage and struct rlimit for
> system calls.  But x32 log is 32-bit.  This patch change uapi
> <linux/resource.h> to use __kernel_long_t in struct rusage and
> __kernel_ulong_t in and struct rlimit.

 a) please send all your related patches as a series
 b) explain how these changes to shared ABI headers:

     1) do not break any architecture, especially mips N32 which is
        the MIPS equivalent of x32
     2) do not break existing x32 binaries
     3) fix existing and future x32 binaries

 c) why you suddenly need these changes now and not when the x32 ABI
    support was submitted and hopefully heavily tested

  reply	other threads:[~2013-12-26 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-25 14:54 [PATCH] Use __kernel_long_t/__kernel_ulong_t in <linux/resource.h> H.J. Lu
2013-12-26 10:03 ` Christoph Hellwig [this message]
2013-12-26 13:52   ` H.J. Lu
2013-12-26 13:54     ` H.J. Lu
2013-12-26 17:58     ` H. Peter Anvin
2013-12-26 18:08       ` H.J. Lu
2013-12-26 19:13     ` H. Peter Anvin
2013-12-26 15:36 ` H.J. Lu

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=20131226100348.GA7751@infradead.org \
    --to=hch@infradead.org \
    --cc=hjl.tools@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox