From: jbarnes@sgi.com (Jesse Barnes)
To: "H. J. Lu" <hjl@lucon.org>
Cc: davidm@hpl.hp.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: milstone reached: ia64 linux builds out of Linus' tree
Date: Mon, 4 Aug 2003 11:52:31 -0700 [thread overview]
Message-ID: <20030804185231.GA532@sgi.com> (raw)
In-Reply-To: <20030804181033.GA17265@lucon.org>
Thanks H.J., this patch works for me! I had to add one more for xfs
(included), but after that, things seemed to work.
Thanks,
Jesse
On Mon, Aug 04, 2003 at 11:10:33AM -0700, H. J. Lu wrote:
> On Mon, Aug 04, 2003 at 11:00:16AM -0700, Jesse Barnes wrote:
> > On Mon, Aug 04, 2003 at 10:53:08AM -0700, H. J. Lu wrote:
> > > On Mon, Aug 04, 2003 at 10:37:39AM -0700, David Mosberger wrote:
> > > > As of this morning, Linus's current bk tree
> > > > (http://linux.bkbits.net:8080/linux-2.5) builds and works out of the
> > > > box for ia64!
> > > >
> > >
> > > Does it work on bigsur? Does it support kernel modules?
> >
> > I just tried the latest on my big sur, and though I think modules work
> > (at least they build for other machines), big sur is broken because
> > non-ACPI based PCI enumeration has been removed from the tree.
> >
>
> Can you try this patch for bigsur?
diff -Nru a/fs/xfs/linux/xfs_vfs.h b/fs/xfs/linux/xfs_vfs.h
--- a/fs/xfs/linux/xfs_vfs.h Wed Jul 16 12:10:39 2003
+++ b/fs/xfs/linux/xfs_vfs.h Wed Jul 16 12:10:39 2003
@@ -44,8 +44,8 @@
typedef struct vfs {
u_int vfs_flag; /* flags */
- fsid_t vfs_fsid; /* file system ID */
- fsid_t *vfs_altfsid; /* An ID fixed for life of FS */
+ __kernel_fsid_t vfs_fsid; /* file system ID */
+ __kernel_fsid_t *vfs_altfsid; /* An ID fixed for life of FS */
bhv_head_t vfs_bh; /* head of vfs behavior chain */
struct super_block *vfs_super; /* Linux superblock structure */
struct task_struct *vfs_sync_task;
diff -Nru a/fs/xfs/xfs_mount.c b/fs/xfs/xfs_mount.c
--- a/fs/xfs/xfs_mount.c Wed Jul 16 12:10:39 2003
+++ b/fs/xfs/xfs_mount.c Wed Jul 16 12:10:39 2003
@@ -889,7 +889,7 @@
* File systems that don't support user level file handles (i.e.
* all of them except for XFS) will leave vfs_altfsid as NULL.
*/
- vfsp->vfs_altfsid = (fsid_t *)mp->m_fixedfsid;
+ vfsp->vfs_altfsid = (__kernel_fsid_t *)mp->m_fixedfsid;
mp->m_dmevmask = 0; /* not persistent; set after each mount */
/*
next prev parent reply other threads:[~2003-08-04 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 17:37 milstone reached: ia64 linux builds out of Linus' tree David Mosberger
2003-08-04 17:53 ` H. J. Lu
2003-08-04 18:00 ` Jesse Barnes
2003-08-04 18:10 ` H. J. Lu
2003-08-04 18:52 ` Jesse Barnes [this message]
2003-08-04 19:18 ` Andreas Schwab
2003-08-04 18:27 ` David Mosberger
2003-08-04 18:49 ` Jesse Barnes
2003-08-04 18:21 ` David Mosberger
2003-08-04 18:41 ` Jes Sorensen
2003-08-04 18:31 ` David S. Miller
2003-08-04 18:40 ` David Mosberger
2003-08-04 18:45 ` David S. Miller
2003-08-04 19:07 ` Alan Cox
2003-08-04 19:17 ` David S. Miller
2003-08-04 23:06 ` Peter Chubb
2003-08-04 23:35 ` David Mosberger
2003-08-13 0:07 ` Ian Wienand
2003-09-10 0:53 ` Ian Wienand
2003-09-10 1:57 ` David Mosberger
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=20030804185231.GA532@sgi.com \
--to=jbarnes@sgi.com \
--cc=davidm@hpl.hp.com \
--cc=hjl@lucon.org \
--cc=linux-ia64@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).