From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Joe Perches <joe@perches.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Adrian Hunter <adrian.hunter@nokia.com>,
Alex Elder <aelder@sgi.com>,
Artem Bityutskiy <dedekind@infradead.org>,
Christoph Hellwig <hch@lst.de>,
Harvey Harrison <harvey.harrison@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Jeff Garzik <jgarzik@redhat.com>,
Matt Mackall <mpm@selenic.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Neil Brown <neilb@suse.de>,
Steven Whitehouse <swhiteho@redhat.com>,
"xfs-masters@oss.sgi.com" <xfs-masters@oss.sgi.com>,
Andi Kleen <andi@firstfloor.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH 0/9] Add vsprintf extension %pU to print UUID/GUIDs and use it
Date: Thu, 1 Oct 2009 02:07:45 +0200 [thread overview]
Message-ID: <200910010207.45514.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <1254203852.15717.1506.camel@yhuang-dev.sh.intel.com>
On Tuesday 29 September 2009 07:57:32 Huang Ying wrote:
> Hi, Joe,
>
> Thanks for the patch. I think that is a good idea.
>
> For your patch. I think you need a changelog for each patch.
>
> It seems that the binary representation of UUID can be little-endian
> (used by most kernel components) or big-endian (defined by RFC4122, used
> in network?). Maybe we should consider about that.
I think that's what the 'r' option is supposed to handle. Maybe you could use
'b' and 'l' options instead, to specify the endianness explicitly.
> In fact, I find there are many different UUID/GUID definitions in
> kernel, such as that in efi, many file systems, some drivers, etc. It
> seems that every kernel components need UUID/GUID has its own
> definition, so I think we should unify all the UUID/GUID definitions in
> kernel too. The file attached is a draft unified UUID/GUID definition,
> with byte-order issue in mind.
>
> Any comment?
Not much, it would help if you could show where those functions would be used.
I would also use the 'le' and 'be' prefixes (as in le16, be32) instead of 'l'
and 'b', making it leuuid and beuuid, or maybe uuid_le and uuid_be.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2009-10-01 0:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 5:01 Joe Perches
2009-09-29 5:01 ` [PATCH 1/9] lib/vsprintf.c: Add %pU to print UUID/GUIDs Joe Perches
2009-10-01 7:10 ` Geert Uytterhoeven
2009-10-01 7:26 ` Joe Perches
2009-10-01 8:55 ` Geert Uytterhoeven
2009-10-07 0:07 ` Joe Perches
2009-09-29 5:01 ` [PATCH 2/9] efi.h: Use %pUr to print UUIDs Joe Perches
2009-09-29 5:01 ` [PATCH 3/9] random.c: Use %pU " Joe Perches
2009-09-29 5:01 ` [PATCH 4/9] drivers/firmware/dmi_scan.c: Use %pUX " Joe Perches
2009-09-29 5:01 ` [PATCH 5/9] drivers/md/md.c: Use %pU " Joe Perches
2009-09-29 5:01 ` [PATCH 6/9] drivers/media/video/uvc: Use %pUr " Joe Perches
2009-10-01 0:20 ` Laurent Pinchart
2009-10-01 0:24 ` Joe Perches
2009-09-29 5:01 ` [PATCH 7/9] fs/gfs2/sys.c: Use %pUX " Joe Perches
2009-09-29 8:50 ` Steven Whitehouse
2009-09-29 5:01 ` [PATCH 8/9] fs/ubifs: " Joe Perches
2009-09-29 12:32 ` Artem Bityutskiy
2009-09-29 5:01 ` [PATCH 9/9] fs/xfs/xfs_log_recover.c: Use %pU " Joe Perches
2009-09-29 5:57 ` [PATCH 0/9] Add vsprintf extension %pU to print UUID/GUIDs and use it Huang Ying
2009-10-01 0:07 ` Laurent Pinchart [this message]
2009-10-01 0:20 ` Joe Perches
2009-10-10 5:50 ` Huang Ying
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=200910010207.45514.laurent.pinchart@ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=adrian.hunter@nokia.com \
--cc=aelder@sgi.com \
--cc=andi@firstfloor.org \
--cc=dedekind@infradead.org \
--cc=greg@kroah.com \
--cc=harvey.harrison@gmail.com \
--cc=hch@lst.de \
--cc=jgarzik@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=neilb@suse.de \
--cc=swhiteho@redhat.com \
--cc=xfs-masters@oss.sgi.com \
--cc=ying.huang@intel.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®