mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: akpm@linux-foundation.org
Cc: wcohen@redhat.com, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org, ralf@linux-mips.org
Subject: reduce-size-of-task_struct-on-64-bit-machines.patch removed from -mm tree
Date: Tue, 29 May 2007 17:55:01 -0400	[thread overview]
Message-ID: <20070529215501.GA15944@fattire.cabal.ca> (raw)
In-Reply-To: <200705090244.l492i4kH008542@shell0.pdx.osdl.net>

On Tue, May 08, 2007 at 07:44:04PM -0700, akpm@linux-foundation.org wrote:
> -	unsigned long flags;	/* per process flags, defined below */
> -	unsigned long ptrace;
> +	unsigned int flags;	/* per process flags, defined below */
> +	unsigned int ptrace;
>  

So.

I realize I don't have much right to cry over spilled milk here, seeing
as this has been floating around for, what, four months now?

But seriously, if people are going to fuck around with extremely core
pieces of generic code, could they please check all the users[1]?

Other 64-bit arch maintainers should check that they're using a 32-bit
load/store on these fields in their assembly now (we were using a
#define to do word on 32bit and doubleword on 64bit, which broke, badly,
when these changed.)

Thanks,
	Kyle M.

1: Adding __deprecated or something to the field would give you an idea
of where it is used, in this case asm-offsets.c...

       reply	other threads:[~2007-05-29 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705090244.l492i4kH008542@shell0.pdx.osdl.net>
2007-05-29 21:55 ` Kyle McMartin [this message]
2007-05-30  1:10   ` Kyle McMartin

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=20070529215501.GA15944@fattire.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=wcohen@redhat.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

all inboxes | Powered by JetHome®