From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Konrad Gräfe" <k.graefe@gateware.de>
Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Andrzej Pietrasiewicz <andrzej.p@collabora.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v4 1/2] vsprintf: Add %p[mM]U for uppercase MAC address
Date: Tue, 2 May 2023 23:03:42 +0300 [thread overview]
Message-ID: <ZFFsni5znI4hS953@smile.fi.intel.com> (raw)
In-Reply-To: <20230428064905.145858-1-k.graefe@gateware.de>
On Fri, Apr 28, 2023 at 08:49:04AM +0200, Konrad Gräfe wrote:
> The CDC-ECM specification requires an USB gadget to send the host MAC
> address as uppercase hex string. This change adds the appropriate
> modifier.
Why not teaching %ph to provide an uppercase? Would be much more useful than
this.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-05-02 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2023042625-rendition-distort-fe06@gregkh>
2023-04-27 11:51 ` [PATCH v3 1/2] vsprintf: Add %p[mM]U for uppercase MAC address Konrad Gräfe
2023-04-27 11:51 ` [PATCH v3 2/2] usb: gadget: u_ether: Fix host MAC address case Konrad Gräfe
2023-04-28 6:49 ` [PATCH v4 1/2] vsprintf: Add %p[mM]U for uppercase MAC address Konrad Gräfe
2023-04-28 6:49 ` [PATCH v4 2/2] usb: gadget: u_ether: Fix host MAC address case Konrad Gräfe
2023-05-02 20:03 ` Andy Shevchenko [this message]
2023-05-05 14:36 ` [PATCH v5] " Konrad Gräfe
2023-04-27 12:26 ` [PATCH v3 1/2] vsprintf: Add %p[mM]U for uppercase MAC address Greg Kroah-Hartman
2023-04-27 12:35 ` Rasmus Villemoes
2023-04-27 14:26 ` Konrad Gräfe
2023-04-27 21:30 ` Peter Seiderer
2023-04-28 6:56 ` Rasmus Villemoes
2023-04-28 7:19 ` Greg Kroah-Hartman
2023-04-28 7:46 ` David Laight
2023-05-02 20:01 ` Andy Shevchenko
2023-05-02 12:23 ` Petr Mladek
2023-05-04 13:25 ` Konrad Gräfe
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=ZFFsni5znI4hS953@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andrzej.p@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.graefe@gateware.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=quentin.schulz@theobroma-systems.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
/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