All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: vonbrand@inf.utfsm.cl, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: Linux 2.4.15-pre4 - merge with Alan
Date: Wed, 14 Nov 2001 07:28:52 +0100	[thread overview]
Message-ID: <20011114072852.A16556@suse.de> (raw)
In-Reply-To: <torvalds@transmeta.com> <200111131410.fADEA9L8023291@pincoya.inf.utfsm.cl> <20011113162102.A2305@suse.de> <20011113.205729.71087461.davem@redhat.com>
In-Reply-To: <20011113.205729.71087461.davem@redhat.com>; from davem@redhat.com on Tue, Nov 13, 2001 at 08:57:29PM -0800

On Tue, Nov 13, David S. Miller wrote:

> 
> This first patch is wrong.  lv_block_exception needs translating
> because the types are of a different size on sparc32 than on sparc64.
> 
> Specifically the first member of lv_block_exception_t is
> 'struct list_head', which are two pointers, which is 8 bytes
> on sparc32 and 16 bytes on sparc64.
> 
> Please do not apply these patches.

If the first one should be wrong, why not apply the second one ?
Or I'm missing something ?
To the first patch: Without it you will always get a kernel oops
in this part of ioctl32.c

  Thorsten

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE GmbH            Deutschherrenstr. 15-19       D-90429 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B

  reply	other threads:[~2001-11-14  6:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 19:01 Linux 2.4.15-pre4 - merge with Alan Linus Torvalds
2001-11-12 19:18 ` Trever L. Adams
2001-11-13 11:14   ` Christoph Rohland
2001-11-12 19:26 ` Matthew Dharm
2001-11-12 20:09 ` Martin Dalecki
2001-11-12 20:42 ` Greg KH
2001-11-12 23:43 ` J . A . Magallon
2001-11-13  1:11   ` Alan Cox
2001-11-12 23:45 ` J . A . Magallon
2001-11-12 23:48 ` J . A . Magallon
2001-11-13  0:14   ` Christoph Hellwig
2001-11-13  0:25     ` J . A . Magallon
2001-11-13  0:42     ` J . A . Magallon
2001-11-13  7:43       ` Christoph Hellwig
2001-11-13  5:17 ` Keith Owens
2001-11-13 10:43   ` David S. Miller
2001-11-13 17:27   ` Chad N. Tindel
2001-11-13 17:58     ` Chad N. Tindel
2001-11-13  5:54 ` Neil Brown
2001-11-13  6:02   ` Jeff Garzik
2001-11-13  9:41     ` Alan Cox
2001-11-13  6:03   ` David S. Miller
2001-11-13  6:16     ` Keith Owens
2001-11-13  6:23       ` David S. Miller
2001-11-13  8:17         ` Jeff Garzik
2001-11-13  6:18     ` Keith Owens
2001-11-13 14:10 ` Horst von Brand
2001-11-13 15:21   ` Thorsten Kukuk
2001-11-14  4:57     ` David S. Miller
2001-11-14  6:28       ` Thorsten Kukuk [this message]
2001-11-14  6:31         ` David S. Miller
2001-11-14 12:59     ` Horst von Brand
2001-11-13 15:37 ` [PATCH] " Russell King
2001-11-15  9:25 ` Problem with Linux 2.4.15-pre4 on an IBM ThinkPad Martin Persson
2001-11-15 11:57   ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-11-12 21:10 Linux 2.4.15-pre4 - merge with Alan Robert Cantu
2001-11-13 13:20 ` Andrey Savochkin

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=20011114072852.A16556@suse.de \
    --to=kukuk@suse.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=vonbrand@inf.utfsm.cl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.