From: "Mark Peloquin" <peloquin@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: [PATCH] EVMS core 1/4: evms.c
Date: Fri, 4 Oct 2002 12:07:05 -0500 [thread overview]
Message-ID: <OF9683DE97.19D23CC6-ON85256C48.005CD740@pok.ibm.com> (raw)
On Friday 04 October 2002 09:56, Christoph Hellwig wrote:
> > +/**
> > + * find_next_volume - locates first or next logical volume
> > + * @lv: current logical volume
> > + *
> > + * returns the next logical volume or NULL
> > + **/
>
> All user of this look like they better used list_for_each?
>
> > +
> > +/**
> > + * find_next_volume_safe - locates first or next logical volume (safe
> > for removes) + * @next_lv: ptr to next logical volume
> > + *
> > + * returns the next logical volume or NULL
> > + **/
>
> Dito with list_for_each_safe
This was done to abstract the storage/lookup
method. Currently with only 256 minors per major
a simply kernel list is adequate, however once
the kernel goes to 20-bit minors a list will not
be sufficient.
next reply other threads:[~2002-10-04 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 17:07 Mark Peloquin [this message]
2002-10-04 17:04 ` Christoph Hellwig
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=OF9683DE97.19D23CC6-ON85256C48.005CD740@pok.ibm.com \
--to=peloquin@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=hch@infradead.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
all inboxes | Powered by JetHome®