net: ena: remove h from printk format specifier
Subsystems (3)
PATCH 1/1 net: ena: remove h from printk format specifier
From: Tom Rix <[email protected]>
This change fixes the checkpatch warning described in this commit
commit cbacb5ab0aa0 ("docs: printk-formats: Stop encouraging use of unnecessary %h[xudi] and %hh[xudi]")
Standard integer promotion is already done and %hx and %hhx is useless so do not encourage the use of %hh[xudi] or %h[xudi].
--- drivers/net/ethernet/amazon/ena/ena_com.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/amazon/ena/ena_com.c +2 -2
@@ -863,7 +863,7 @@ static u32 ena_com_reg_bar_read32(struct ena_com_dev *ena_dev, u16 offset)if (unlikely (i == timeout)) {netdev_err (ena_dev->net_device, -"Reading reg failed for timeout. expected: req id[%hu] offset[%hu] actual: req id[%hu] offset[%hu]\n" , +"Reading reg failed for timeout. expected: req id[%u] offset[%u] actual: req id[%u] offset[%u]\n" , mmio_read->seq_num, offset, read_resp->req_id, read_resp->reg_off); ret =ENA_MMIO_READ_TIMEOUT ;
@@ -2396,7 +2396,7 @@ int ena_com_fill_hash_function(struct ena_com_dev *ena_dev,if (key) {if (key_len !=sizeof (hash_key->key)) {netdev_err (ena_dev->net_device, -"key len (%hu) doesn't equal the supported size (%zu)\n" , +"key len (%u) doesn't equal the supported size (%zu)\n" , key_len,sizeof (hash_key->key));return -EINVAL ; }
Signature · 1 line
2.27.0
Jakub Kicinski
maintainerQuoted 9 lines · On Wed, 23 Dec 2020 11:31:44 -0800 [email protected] wrote:
From: Tom Rix <[email protected]>
This change fixes the checkpatch warning described in this commit
commitcbacb5ab0aa0("docs: printk-formats: Stop encouraging use of unnecessary %h[xudi] and %hh[xudi]")Standard integer promotion is already done and %hx and %hhx is useless so do not encourage the use of %hh[xudi] or %h[xudi].
Signed-off-by Tom Rix <[email protected]>
This really is not a change worth making in existing code, IMO.
I find it a little ironic that nacking of unnecessary code churn has spawned unnecessary code churn in the opposite direction.
I'd leave it up to maintainers of specific drivers to decide, but for now - net-next is closed anyway, please come back with these after merge window is over.
Thanks!