public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ricardo M. Correia" <Ricardo.M.Correia@Sun.COM>
To: Karel Zak <kzak@redhat.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	linux-ext4@vger.kernel.org, Andreas Dilger <adilger@Sun.COM>
Subject: Re: [PATCH e2fsprogs] Add ZFS detection to libblkid
Date: Mon, 02 Jun 2008 16:03:20 +0100	[thread overview]
Message-ID: <1212419000.7337.36.camel@localhost> (raw)
In-Reply-To: <20080602074102.GA3242@nb.net.home>

Hi Karel,

On Seg, 2008-06-02 at 09:41 +0200, Karel Zak wrote: 
> It'd be nice to add ZFS detection to libvolume_id from udev package.

Interesting, I didn't know libvolume_id existed.
Is there a reason why there should be 2 different libraries doing what
appears to be essentially the same thing?

> > +	/* read nvpair data for pool name, pool GUID (complex) */
> > +	//blkid_set_tag(probe->dev, "LABEL", pool_name, sizeof(pool_name));
> > +	//set_uuid(probe->dev, pool_guid, 0);
> 
>  C++ ?

Actually, those are valid C99 tokens for comments. I don't see any style
guide in the source of e2fsprogs, and they do appear to be used in some
places (like lib/uuid/uuid_gen_nt.c), but if necessary that can be
easily changed.

> > -		if (memcmp(id->bim_magic, buf + (id->bim_sboff&0x3ff),
> > +		if (memcmp(id->bim_magic, buf + (id->bim_sboff & 0x3ff),
> 
>  ???

That's unrelated to the purpose of this patch, it seems to be just a
style fix (inherited from Andreas' patch) :-)

Thanks,
Ricardo

--

Ricardo Manuel Correia
Lustre Engineering

Sun Microsystems, Inc.
Portugal
Phone +351.214134023 / x58723
Mobile +351.912590825
Email Ricardo.M.Correia@Sun.COM


  reply	other threads:[~2008-06-02 15:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 18:20 [PATCH e2fsprogs] Add ZFS detection to libblkid Ricardo M. Correia
2008-06-02  7:41 ` Karel Zak
2008-06-02 15:03   ` Ricardo M. Correia [this message]
     [not found]   ` <1212418863.7337.34.camel@localhost>
2008-06-02 20:58     ` Karel Zak
2008-06-02 21:38       ` Andreas Dilger
2008-06-02 22:31         ` Karel Zak
2008-06-02 23:11           ` Andreas Dilger
2008-06-03  0:05       ` Theodore Tso
2008-06-03  1:11 ` Theodore Tso
2009-04-04  2:39 ` Eric Sandeen
2009-04-04 13:04   ` Eric Sandeen
2009-04-04 21:25     ` Andreas Dilger
2009-04-04 21:46       ` Eric Sandeen
2009-04-06  6:25         ` Andreas Dilger
2009-04-06 19:22       ` Ricardo M. Correia
2009-04-06 20:13         ` Eric Sandeen
2009-04-13 19:18           ` Ricardo M. Correia
2009-04-13 19:27             ` Eric Sandeen
2009-04-06 20:35         ` Karel Zak
2009-04-07  7:40         ` Andreas Dilger
2009-04-13 19:29           ` Ricardo M. Correia
2009-04-17  9:51             ` Karel Zak

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=1212419000.7337.36.camel@localhost \
    --to=ricardo.m.correia@sun.com \
    --cc=adilger@Sun.COM \
    --cc=kzak@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.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