public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: "Ghozlane Toumi" <gtoumi@laposte.net>
Cc: <Andries.Brouwer@cwi.nl>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sgi partitionning fix (Was: 2.6.0-test1 on alpha : disk label numbering trouble)
Date: Tue, 29 Jul 2003 01:09:51 +0200	[thread overview]
Message-ID: <20030728230951.GC1845@win.tue.nl> (raw)
In-Reply-To: <041201c35551$8af611c0$0a00a8c0@toumi>

On Mon, Jul 28, 2003 at 11:45:12PM +0200, Ghozlane Toumi wrote:

> However, I found out that sgi partitionning had this "renumbering"
> issue even before viro's patch.
> I don't know if this is correct, in any case this is an untested patch
> that changes this behaviour for sgi partitions.
> patch is attached because of dumb mailer.
> --------------------
>         for(i = 0; i < 16; i++, p++) {
>                 blocks = be32_to_cpu(p->num_blocks);
>                 start  = be32_to_cpu(p->first_block);
>                 if (blocks)
> -                       put_partition(state, slot++, start, blocks);
> +                       put_partition(state, i+1, start, blocks);
>         }
> --------------------

Hmm. The previous change was not because there is something
intrinsically good with some way of numbering partitions,
but because it is very inconvenient when partition numbering
changes.

Thus, the previous patch made OSF in 2.6 do as it did in 2.4.

But here the 2.6 behaviour is already that of 2.4.21, and you
change away from that. Not a good idea.

Andries


  reply	other threads:[~2003-07-28 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 13:15 [PATCH] Re: 2.6.0-test1 on alpha : disk label numbering trouble Andries.Brouwer
2003-07-28 13:54 ` Ghozlane Toumi
2003-07-28 21:45   ` [PATCH] sgi partitionning fix (Was: 2.6.0-test1 on alpha : disk label numbering trouble) Ghozlane Toumi
2003-07-28 23:09     ` Andries Brouwer [this message]
2003-07-29 11:00       ` Ghozlane Toumi

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=20030728230951.GC1845@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=gtoumi@laposte.net \
    --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