From: Huang Ying <ying.huang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>,
Steven Whitehouse <swhiteho@redhat.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [RFC 0/2] Unified UUID/GUID definition
Date: Wed, 14 Oct 2009 14:30:03 +0800 [thread overview]
Message-ID: <1255501803.6047.1191.camel@yhuang-dev.sh.intel.com> (raw)
Hi, All,
This patchset is an attempt to provide a unified UUID/GUID definition to
replace various UUID/GUID definitions in current kernel. This will make
kernel source more readable and unify some duplicated efforts.
This is a RFC to talk about the general UUID/GUID definition design.
Only
UUID/GUID is used by many modules/subsystems in kernel. But this
patchset only replace one of them to use the new definition as an
example. After consensus is reached, we can replace other UUID/GUID
usage too.
This patchset is based on Joe's UUID printk support patchset:
[PATCH 0/9] Add vsprintf extension %pU to print UUID/GUIDs and use it
Any comment is welcome.
Best Regards,
Huang Ying
reply other threads:[~2009-10-14 6:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1255501803.6047.1191.camel@yhuang-dev.sh.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.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®