From: Joe Perches <joe@perches.com>
To: Keith Busch <keith.busch@intel.com>,
linux-nvme@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Cc: Matthew Wilcox <willy@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@infradead.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCHv3] printf: Add format for 8-byte EUI-64 type
Date: Wed, 09 Dec 2015 15:21:40 -0800 [thread overview]
Message-ID: <1449703300.25389.95.camel@perches.com> (raw)
In-Reply-To: <1449702413-25598-1-git-send-email-keith.busch@intel.com>
On Wed, 2015-12-09 at 16:06 -0700, Keith Busch wrote:
> MAC addresses may be formed using rules based on EUI-64, which is 2 bytes
> longer than a typical 6-byte MAC. This patch adds a long specifier to
> the %pM format to support the extended unique identifier.
>
> Since there are multiple valid possible permutations of format specifiers,
> the decoding is done in a loop, and the default ':' separator is
> initialized at declaration time. A side effect of this allows 'F' and
> 'R' both be specified, so these are appended to the documentation.
Just thought of this:
An alternative is using a format of "%8phC"
Is there a use case for a bluetooth or FDDI EUI-64?
WARNING: multiple messages have this Message-ID (diff)
From: joe@perches.com (Joe Perches)
Subject: [PATCHv3] printf: Add format for 8-byte EUI-64 type
Date: Wed, 09 Dec 2015 15:21:40 -0800 [thread overview]
Message-ID: <1449703300.25389.95.camel@perches.com> (raw)
In-Reply-To: <1449702413-25598-1-git-send-email-keith.busch@intel.com>
On Wed, 2015-12-09@16:06 -0700, Keith Busch wrote:
> MAC addresses may be formed using rules based on EUI-64, which is 2 bytes
> longer than a typical 6-byte MAC. This patch adds a long specifier to
> the %pM format to support the extended unique identifier.
>
> Since there are multiple valid possible permutations of format specifiers,
> the decoding is done in a loop, and the default ':' separator is
> initialized at declaration time. A side effect of this allows 'F' and
> 'R' both be specified, so these are appended to the documentation.
Just thought of this:
An alternative is using a format of "%8phC"
Is there a use case for a bluetooth or FDDI EUI-64?
next prev parent reply other threads:[~2015-12-09 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 23:06 [PATCHv3] printf: Add format for 8-byte EUI-64 type Keith Busch
2015-12-09 23:06 ` Keith Busch
2015-12-09 23:21 ` Joe Perches [this message]
2015-12-09 23:21 ` Joe Perches
2015-12-10 15:06 ` Keith Busch
2015-12-10 15:06 ` Keith Busch
2015-12-11 15:42 ` Andy Shevchenko
2015-12-11 15:42 ` Andy Shevchenko
2015-12-10 1:40 ` Elliott, Robert (Persistent Memory)
2015-12-10 1:40 ` Elliott, Robert (Persistent Memory)
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=1449703300.25389.95.camel@perches.com \
--to=joe@perches.com \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=willy@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.