mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: Brian Kress <kressb@fsc-usa.com>
Cc: Mauelshagen@sistina.com, mge@sistina.com, linux-kernel@vger.kernel.org
Subject: Re: RFC: Modularize /proc/partitons (was Re: /proc/partitions for LVM)
Date: Thu, 23 Nov 2000 21:48:38 -0600	[thread overview]
Message-ID: <20001123214838.B8881@wire.cadcamlab.org> (raw)
In-Reply-To: <3A1C3523.A111CDD9@fsc-usa.com> <20001122221152.B4406@srv.t-online.de> <3A1C3A57.9768247B@fsc-usa.com> <20001122235335.C4687@srv.t-online.de> <3A1D7587.D990B92E@fsc-usa.com>
In-Reply-To: <3A1D7587.D990B92E@fsc-usa.com>; from kressb@fsc-usa.com on Thu, Nov 23, 2000 at 02:52:39PM -0500


[Brian Kress]
> 1)  Add a function pointer to struct gendisk called hd_name.
> 
> 2)  Make disk_name in fs/partitions/check.c use that function
>     pointer if its non-null.
> 
> 3)  Change the following drivers to use this method. (adding the
>     driver specific method and removing the old code in check.c)

Looks good to me ... except that cpqarray.c, cciss.c and DAC960.c have
basically duplicate functions.  Would this be a net win:

  char *typical_disk_name(struct gendisk *, int major_base, int minor, char *buf);

...exported from check.c?

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-24  4:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22 21:05 /proc/partitions for LVM Brian Kress
2000-11-22 22:11 ` Heinz J. Mauelshagen
2000-11-22 21:27   ` RFC: Modularize /proc/partitons (was Re: /proc/partitions for LVM) Brian Kress
2000-11-22 23:53     ` Heinz J. Mauelshagen
2000-11-23 19:52       ` Brian Kress
2000-11-24  3:48         ` Peter Samuelson [this message]
2000-11-24 11:48         ` Heinz J. Mauelshagen

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=20001123214838.B8881@wire.cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=Mauelshagen@sistina.com \
    --cc=kressb@fsc-usa.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mge@sistina.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

all inboxes | Powered by JetHome®