The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: "J.A. Magallon" <jamagallon@able.es>, Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19rc3aa4
Date: Wed, 31 Jul 2002 17:54:37 +0200	[thread overview]
Message-ID: <E17Zvo5-0008KY-00@starship> (raw)
In-Reply-To: <20020730143657.GA2224@junk.cps.unizar.es>

On Tuesday 30 July 2002 16:36, J.A. Magallon wrote:
> BTW, are you aware of this in -aa ? I need this patch:
> 
> --- linux/include/asm-i386/processor.h   Fri Jul 19 00:37:45 2002
> +++ linux/include/asm-i386/processor.h~  Fri Jul 19 00:38:48 2002
> @@ -401,7 +401,7 @@
>  	{ [0 ... 7] = 0 },	/* debugging registers */	\
>  	0, 0, 0,						\
>  	{ { 0, }, },		/* 387 state */			\
> -	0,0,0,0,0,0,						\
> +	0,0,0,0,0,						\
>  	0,{~0,}			/* io permissions */		\
>  }
>  
> to shut up gcc and match the struct definition:
> 
> /* floating point info */
>     union i387_union    i387;
> /* virtual 86 mode info */
>     struct vm86_struct  * vm86_info;
>     unsigned long       screen_bitmap;
>     unsigned long       v86flags, v86mask, saved_esp0;
> /* IO permissions */
>     int     ioperm;
>     unsigned long   io_bitmap[IO_BITMAP_SIZE+1];
> 
> Coud be serious to have io_bitmap == 0 instead of == ~0 ??

It should be written "= {.io_bitmap = {~0}}" but that's still
bogus: only the first array element gets the ones, probably not 
what was intended.

-- 
Daniel

  reply	other threads:[~2002-07-31 15:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30  6:02 2.4.19rc3aa4 Andrea Arcangeli
2002-07-30  8:42 ` 2.4.19rc3aa4 Christoph Hellwig
2002-07-30 16:56   ` 2.4.19rc3aa4 Andrea Arcangeli
2002-07-30 14:36 ` 2.4.19rc3aa4 J.A. Magallon
2002-07-31 15:54   ` Daniel Phillips [this message]
2002-07-31 21:08 ` 2.4.19rc3aa4 Benjamin LaHaise
2002-07-31 21:40   ` 2.4.19rc3aa4 Andrea Arcangeli

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=E17Zvo5-0008KY-00@starship \
    --to=phillips@arcor.de \
    --cc=andrea@suse.de \
    --cc=jamagallon@able.es \
    --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