netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v1 1/1] net: ks8851: use %*ph to print small buffer
Date: Thu, 12 Sep 2024 13:06:51 +0100	[thread overview]
Message-ID: <20240912120651.GL572255@kernel.org> (raw)
In-Reply-To: <20240911193630.2884828-1-andriy.shevchenko@linux.intel.com>

On Wed, Sep 11, 2024 at 10:36:30PM +0300, Andy Shevchenko wrote:
> Use %*ph format to print small buffer as hex string.

Hi Andy,

Perhaps it would be worth mentioning that this patch
changes the output format such that there is a space
between each byte rather than each 32-bit word.

Or at least, that is what a local hack on my side indicated
things would look like :)

> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  drivers/net/ethernet/micrel/ks8851_common.c | 19 +------------------
>  1 file changed, 1 insertion(+), 18 deletions(-)
> 
> diff --git a/drivers/net/ethernet/micrel/ks8851_common.c b/drivers/net/ethernet/micrel/ks8851_common.c
> index 7fa1820db9cc..a07ffc53da64 100644
> --- a/drivers/net/ethernet/micrel/ks8851_common.c
> +++ b/drivers/net/ethernet/micrel/ks8851_common.c
> @@ -215,22 +215,6 @@ static void ks8851_init_mac(struct ks8851_net *ks, struct device_node *np)
>  	ks8851_write_mac_addr(dev);
>  }
>  
> -/**
> - * ks8851_dbg_dumpkkt - dump initial packet contents to debug
> - * @ks: The device state
> - * @rxpkt: The data for the received packet
> - *
> - * Dump the initial data from the packet to dev_dbg().
> - */
> -static void ks8851_dbg_dumpkkt(struct ks8851_net *ks, u8 *rxpkt)
> -{
> -	netdev_dbg(ks->netdev,
> -		   "pkt %02x%02x%02x%02x %02x%02x%02x%02x %02x%02x%02x%02x\n",
> -		   rxpkt[4], rxpkt[5], rxpkt[6], rxpkt[7],
> -		   rxpkt[8], rxpkt[9], rxpkt[10], rxpkt[11],
> -		   rxpkt[12], rxpkt[13], rxpkt[14], rxpkt[15]);
> -}
> -
>  /**
>   * ks8851_rx_pkts - receive packets from the host
>   * @ks: The device information.
> @@ -296,8 +280,7 @@ static void ks8851_rx_pkts(struct ks8851_net *ks, struct sk_buff_head *rxq)
>  
>  				ks->rdfifo(ks, rxpkt, rxalign + 8);
>  
> -				if (netif_msg_pktdata(ks))
> -					ks8851_dbg_dumpkkt(ks, rxpkt);
> +				netif_dbg(ks, pktdata, ks->netdev, "pkt %12ph\n", &rxpkt[4]);

nit: I would have line wrapped this so it is <= 80 columns wide.

>  
>  				skb->protocol = eth_type_trans(skb, ks->netdev);
>  				__skb_queue_tail(rxq, skb);
> -- 
> 2.43.0.rc1.1336.g36b5255a03ac
> 
> 

      reply	other threads:[~2024-09-12 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 19:36 [PATCH net-next v1 1/1] net: ks8851: use %*ph to print small buffer Andy Shevchenko
2024-09-12 12:06 ` Simon Horman [this message]

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=20240912120651.GL572255@kernel.org \
    --to=horms@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).