public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt_Domsch@Dell.com
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] select EFI partition support by default
Date: Mon, 13 Oct 2003 15:37:50 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106605963631800@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106588409310269@msgid-missing>

On Mon, 2003-10-13 at 10:21, John Levon wrote:
> On Mon, Oct 13, 2003 at 10:00:47AM +0100, Christoph Hellwig wrote:
> 
> > > > +       bool "EFI GUID Partition support" if PARTITION_ADVANCED
> > > > +       default y if !PARTITION_ADVANCED && IA64
> > > 
> > > Can we make CONFIG_LBD force on CONFIG_EFI_PARTITION too then?
> > 
> > I know the LBD backport is used with SGI disklabels in production
> > enviroments.  In fact that's the only production use I know of at
> all...
> 
> Besides, unless I'm missing something, current 2.6 doesn't prompt for
> LBD for IA64 at all ?
> 
> So, anybody want the patch :)

Actually, CONFIG_LBD is not necessary on IA-64.

include/linux/types.h:

 * The type used for indexing onto a disc or disc partition.
 * If required, asm/types.h can override it and define
 * HAVE_SECTOR_T
 */
#ifndef HAVE_SECTOR_T
typedef unsigned long sector_t;
#endif

Since HAVE_SECTOR_T isn't ever defined by IA-64, this does the right
thing.


-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com


  parent reply	other threads:[~2003-10-13 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-11 14:54 [PATCH] select EFI partition support by default John Levon
2003-10-11 16:11 ` Matt Domsch
2003-10-13  9:00 ` Christoph Hellwig
2003-10-13 15:21 ` John Levon
2003-10-13 15:37 ` Matt_Domsch [this message]
2003-10-13 20:55 ` Peter Chubb

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=marc-linux-ia64-106605963631800@msgid-missing \
    --to=matt_domsch@dell.com \
    --cc=linux-ia64@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