From: Larry Finger <Larry.Finger@lwfinger.net>
To: Mike Krinkin <krinkin.m.u@gmail.com>, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8188eu: use %*ph specifier instead of passing direct values
Date: Sun, 08 Mar 2015 11:23:05 -0500 [thread overview]
Message-ID: <54FC7769.7050306@lwfinger.net> (raw)
In-Reply-To: <1425830070-4948-1-git-send-email-krinkin.m.u@gmail.com>
On 03/08/2015 10:54 AM, Mike Krinkin wrote:
> The %*ph specifier allows to pass a pointer and length instead of
> pushing each byte via stack. The patch converts code to use it.
>
> Signed-off-by: Mike Krinkin <krinkin.m.u@gmail.com>
Why not use %pM as long as you are changing this code? It will format the
results in a better way.
Larry
> ---
> drivers/staging/rtl8188eu/hal/usb_halinit.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/rtl8188eu/hal/usb_halinit.c b/drivers/staging/rtl8188eu/hal/usb_halinit.c
> index 122e9b3..960a7a5 100644
> --- a/drivers/staging/rtl8188eu/hal/usb_halinit.c
> +++ b/drivers/staging/rtl8188eu/hal/usb_halinit.c
> @@ -1096,10 +1096,8 @@ static void Hal_EfuseParseMACAddr_8188EU(struct adapter *adapt, u8 *hwinfo, bool
> memcpy(eeprom->mac_addr, &hwinfo[EEPROM_MAC_ADDR_88EU], ETH_ALEN);
> }
> RT_TRACE(_module_hci_hal_init_c_, _drv_notice_,
> - ("Hal_EfuseParseMACAddr_8188EU: Permanent Address = %02x-%02x-%02x-%02x-%02x-%02x\n",
> - eeprom->mac_addr[0], eeprom->mac_addr[1],
> - eeprom->mac_addr[2], eeprom->mac_addr[3],
> - eeprom->mac_addr[4], eeprom->mac_addr[5]));
> + ("Hal_EfuseParseMACAddr_8188EU: Permanent Address = %6phD\n",
> + eeprom->mac_addr));
> }
>
> static void
>
next prev parent reply other threads:[~2015-03-08 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 15:54 [PATCH] staging: rtl8188eu: use %*ph specifier instead of passing direct values Mike Krinkin
2015-03-08 16:23 ` Larry Finger [this message]
2015-03-08 16:41 ` Mike Krinkin
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=54FC7769.7050306@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=krinkin.m.u@gmail.com \
--cc=linux-kernel@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