From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/3] lx6464es: dump MAC in standard form
Date: Wed, 29 May 2013 14:31:07 +0300 [thread overview]
Message-ID: <1369827067.29283.237.camel@smile> (raw)
In-Reply-To: <s5hy5ay59qc.wl%tiwai@suse.de>
On Wed, 2013-05-29 at 13:03 +0200, Takashi Iwai wrote:
> > > > - sprintf(card->shortname, "LX6464ES %02X.%02X.%02X.%02X.%02X.%02X",
> > > > - chip->mac_address[0], chip->mac_address[1], chip->mac_address[2],
> > > > - chip->mac_address[3], chip->mac_address[4], chip->mac_address[5]);
> > > > + sprintf(card->shortname, "LX6464ES %pM", chip->mac_address);
> > >
> > > This will change from the upper to the lower case, thus it'll lead to
> > > an incompatible name string, unfortunately.
> >
> > Who is the user of this string?
>
> It's exposed to the user-space via ioctl and it can be used as an id
> string. So this will break user-space compatibility.
MAC is theoretically set of arbitrary 6 bytes.
Only what I can see here is the difference between '.' and ':' as a
delimiter. But the MAC address form is defined in IEEE 802 standards.
Anyway, I am okay if you reject this one.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2013-05-29 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 10:03 [PATCH 1/3] lx6464es: remove useles pci_set_drvdata(pdev, NULL) Andy Shevchenko
2013-05-29 10:03 ` [PATCH 2/3] lx6464es: dump MAC in standard form Andy Shevchenko
2013-05-29 10:15 ` Takashi Iwai
2013-05-29 11:00 ` Andy Shevchenko
2013-05-29 11:03 ` Takashi Iwai
2013-05-29 11:31 ` Andy Shevchenko [this message]
2013-05-29 12:15 ` Takashi Iwai
2013-05-29 10:03 ` [PATCH 3/3] lx6464es: use %*phN to print small buffer in hex form Andy Shevchenko
2013-05-29 10:16 ` Takashi Iwai
2013-05-29 11:29 ` Andy Shevchenko
2013-05-29 10:17 ` [PATCH 1/3] lx6464es: remove useles pci_set_drvdata(pdev, NULL) Takashi Iwai
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=1369827067.29283.237.camel@smile \
--to=andriy.shevchenko@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.