public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Joe Perches <joe@perches.com>
Cc: linux-nvme@lists.infradead.org,
	LKML <linux-kernel@vger.kernel.org>,
	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: Thu, 10 Dec 2015 15:06:09 +0000	[thread overview]
Message-ID: <20151210150609.GA23337@localhost.localdomain> (raw)
In-Reply-To: <1449703300.25389.95.camel@perches.com>

On Wed, Dec 09, 2015 at 03:21:40PM -0800, Joe Perches wrote:
> 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?

*facepalm*

I didn't know that format, but it satisfies my needs. I am not aware of
bluetooth or fddi using eui64, so I've no problem withdrawing the patch.
I'll just fix up the one that depended on it.

  reply	other threads:[~2015-12-10 15:07 UTC|newest]

Thread overview: 5+ 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:21 ` Joe Perches
2015-12-10 15:06   ` Keith Busch [this message]
2015-12-11 15:42     ` Andy Shevchenko
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=20151210150609.GA23337@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=axboe@fb.com \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=joe@perches.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox