From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Matt Domsch <mdomsch@Dell.com>
Cc: <torvalds@transmeta.com>, <alan@redhat.com>,
"'Martin.Wilck@Fujitsu-Siemens.com'"
<Martin.Wilck@Fujitsu-Siemens.com>,
"'viro@math.psu.edu'" <viro@math.psu.edu>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] EFI GUID Partition Tables
Date: Tue, 9 Oct 2001 11:25:35 -0600 [thread overview]
Message-ID: <200110091725.f99HPZ530405@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.33.0110091210080.6027-100000@tux.us.dell.com>
In-Reply-To: <Pine.LNX.4.33.0110091210080.6027-100000@tux.us.dell.com>
Matt Domsch writes:
> Prompted by Al Viro's work to move the partition table handling code
> from using block device access to using the page cache, I've pulled
> the EFI GUID Partition Table (GPT) code from the IA-64 port patch
> and updated it. I would like to see it included in the Linus and
> -ac trees, as it barely needs the IA-64 tree, and even then, only
> asm-ia64/efi.h which is already merged. David Mosberger is happy to
> have it dropped from the IA-64 port. This code has been in use on
> IA-64 for quite a while now, so I feel confident that it works.
> I've also used it quite a bit on x86. The devfs GUID support is by
> Martin Wilck.
You've put the devfs_unregister_slave() inside an #ifdef. Yuk! It
shouldn't be conditional. And I'm not really sure that I like this
function in the first place, but that's not something I want to get
into right now.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-10-09 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 17:15 Matt Domsch
2001-10-09 17:25 ` Richard Gooch [this message]
2001-10-12 8:31 ` Martin Wilck
2001-10-12 16:27 ` Andreas Dilger
2001-10-12 14:56 ` Richard Gooch
2001-10-09 21:03 ` Andreas Dilger
2001-10-10 3:01 Matt_Domsch
2001-10-10 4:23 ` Andreas Dilger
2001-10-12 10:12 ` Martin Wilck
2001-10-10 5:18 ` Richard Gooch
2001-10-10 22:08 Matt_Domsch
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=200110091725.f99HPZ530405@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=Martin.Wilck@Fujitsu-Siemens.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdomsch@Dell.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®