public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alistair Strachan <alistair@devzero.co.uk>
To: Badari Pulavarty <pbadari@us.ibm.com>, Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.67-mm1
Date: Wed, 9 Apr 2003 08:00:42 +0100	[thread overview]
Message-ID: <200304090800.43022.alistair@devzero.co.uk> (raw)
In-Reply-To: <200304081606.13405.pbadari@us.ibm.com>

Hi,

On Wednesday 09 April 2003 00:06, Badari Pulavarty wrote:
> On Tuesday 08 April 2003 02:28 pm, Andrew Morton wrote:
> > Ah, good detective work, thanks.  It looks like the hd_struct
> > dynamic allocation patch has broken devfs partition discovery
> > somehow.
>
> Thanks.. I am going to look now. Must have broken something in devfs.
>
> - Badari

Sorry for the delay, I've only just woken up. I applied the patch, it 
wouldn't compile, you missed the following (I think obvious) chunk:

--- linux-2.5/fs/partitions/check.c.old 2003-04-09 07:49:29 +0100
+++ linux-2.5/fs/partitions/check.c     2003-04-09 07:51:26 +0100
@@ -160,7 +160,7 @@
 {
 #ifdef CONFIG_DEVFS_FS
        devfs_handle_t dir;
-       struct hd_struct *p = dev->part;
+       struct hd_struct **p = dev->part;
        char devname[16];

        if (p[part-1]->de)

With that in place, it compiled without warning and the machine now 
boots with the dynamic hd_struct work + aggregate stats patch.

Thanks for your time.

Cheers,
Alistair.


  reply	other threads:[~2003-04-09  6:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 16:41 2.5.67-mm1 Alistair Strachan
2003-04-08 21:28 ` 2.5.67-mm1 Andrew Morton
2003-04-08 23:06   ` 2.5.67-mm1 Badari Pulavarty
2003-04-09  7:00     ` Alistair Strachan [this message]
2003-04-09 15:59       ` 2.5.67-mm1 Badari Pulavarty
2003-04-08 23:24   ` 2.5.67-mm1 Badari Pulavarty
  -- strict thread matches above, loose matches on Subject: below --
2003-04-08 11:22 2.5.67-mm1 Andrew Morton
2003-04-08 13:01 ` 2.5.67-mm1 William Lee Irwin III
2003-04-08 13:17 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 15:31   ` 2.5.67-mm1 Randy.Dunlap
2003-04-08 15:39     ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 16:14       ` 2.5.67-mm1 Randy.Dunlap
2003-04-08 16:18     ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 16:10   ` 2.5.67-mm1 Andrew Morton
2003-04-08 16:50     ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 14:08 ` 2.5.67-mm1 William Lee Irwin III
2003-04-08 16:43 ` 2.5.67-mm1 Helge Hafting

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=200304090800.43022.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.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