linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Calvin Walton <calvin.walton@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] FILESYSTEMS: Make "advanced partitions" immediately unselectable.
Date: Tue, 29 Jul 2008 16:36:53 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0807291635550.13165@localhost.localdomain> (raw)
In-Reply-To: <20080729091707.d82b389a.randy.dunlap@oracle.com>

On Tue, 29 Jul 2008, Randy Dunlap wrote:

> On Tue, 29 Jul 2008 06:36:09 -0400 (EDT) Robert P. J. Day wrote:

> > so, just to be clear, the consensus is to just leave it alone as
> > it's more trouble than it's worth to do anything about?
>
> Probably.
>
> I don't see the "if PARTITION_ADVANCED" block as being compatible
> with the need to have default partition types per $ARCH. Do you see
> some way around that problem?

not presently.  and if i was going to invest more effort, i'd probably
be more tempted to try to reorg the train wreck that is the "Kernel
hacking" submenu, anyway.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

  reply	other threads:[~2008-07-29 20:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26 13:20 [PATCH] FILESYSTEMS: Make "advanced partitions" immediately unselectable Robert P. J. Day
2008-07-26 16:47 ` Randy Dunlap
2008-07-26 21:52   ` Robert P. J. Day
2008-07-28  3:11     ` Calvin Walton
2008-07-28  9:38       ` Robert P. J. Day
2008-07-28 17:37         ` Randy Dunlap
2008-07-28 18:14           ` Robert P. J. Day
2008-07-28 18:42           ` Robert P. J. Day
2008-07-28 18:51             ` Randy Dunlap
2008-07-28 18:56               ` Robert P. J. Day
2008-07-28 21:43             ` Grant Coady
2008-07-28 22:02             ` Calvin Walton
2008-07-28 22:14               ` Randy Dunlap
2008-07-29 10:36                 ` Robert P. J. Day
2008-07-29 16:17                   ` Randy Dunlap
2008-07-29 20:36                     ` Robert P. J. Day [this message]
     [not found] <aTS0O-4U1-33@gated-at.bofh.it>
     [not found] ` <aTV89-39s-5@gated-at.bofh.it>
     [not found]   ` <aTZYh-4i3-21@gated-at.bofh.it>
     [not found]     ` <aUrrl-78m-3@gated-at.bofh.it>
     [not found]       ` <aUxwQ-1Hn-19@gated-at.bofh.it>
     [not found]         ` <aUERB-Zl-5@gated-at.bofh.it>
     [not found]           ` <aUFXh-3m9-3@gated-at.bofh.it>
     [not found]             ` <aUJ4U-1xe-19@gated-at.bofh.it>
     [not found]               ` <aUJeD-1N6-13@gated-at.bofh.it>
     [not found]                 ` <aUUME-5MM-11@gated-at.bofh.it>
     [not found]                   ` <aV05W-1wO-41@gated-at.bofh.it>
2008-08-02 12:41                     ` Bodo Eggert
2008-08-02 14:36                       ` Randy Dunlap
2008-08-02 21:16                         ` Bodo Eggert

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=alpine.LFD.1.10.0807291635550.13165@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=akpm@osdl.org \
    --cc=calvin.walton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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;
as well as URLs for NNTP newsgroup(s).