LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jonathan Lemon <jonathan.lemon@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH v2 net-next 1/1] ptp_ocp: use bits.h macros for all masks
Date: Tue, 17 Aug 2021 06:48:14 -0700	[thread overview]
Message-ID: <20210817064814.13c57002@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210817122454.50616-1-andriy.shevchenko@linux.intel.com>

On Tue, 17 Aug 2021 15:24:54 +0300 Andy Shevchenko wrote:
> Currently we are using BIT(), but GENMASK(). Make use of the latter one
> as well (far less error-prone, far more concise).
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  drivers/ptp/ptp_ocp.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/ptp/ptp_ocp.c b/drivers/ptp/ptp_ocp.c
> index caf9b37c5eb1..922f92637db8 100644
> --- a/drivers/ptp/ptp_ocp.c
> +++ b/drivers/ptp/ptp_ocp.c
> @@ -1,6 +1,7 @@
>  // SPDX-License-Identifier: GPL-2.0-only
>  /* Copyright (c) 2020 Facebook */
>  
> +#include <linux/bits.h>
>  #include <linux/err.h>
>  #include <linux/kernel.h>
>  #include <linux/module.h>
> @@ -84,10 +85,10 @@ struct tod_reg {
>  #define TOD_CTRL_DISABLE_FMT_A	BIT(17)
>  #define TOD_CTRL_DISABLE_FMT_B	BIT(16)
>  #define TOD_CTRL_ENABLE		BIT(0)
> -#define TOD_CTRL_GNSS_MASK	((1U << 4) - 1)
> +#define TOD_CTRL_GNSS_MASK	GENMASK(3, 0)
>  #define TOD_CTRL_GNSS_SHIFT	24
>  
> -#define TOD_STATUS_UTC_MASK	0xff
> +#define TOD_STATUS_UTC_MASK	GENMASK(7, 0)
>  #define TOD_STATUS_UTC_VALID	BIT(8)
>  #define TOD_STATUS_LEAP_VALID	BIT(16)

GENMASK is unsigned long:

drivers/ptp/ptp_ocp.c: In function ‘ptp_ocp_tod_info’:
drivers/ptp/ptp_ocp.c:648:27: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘long unsigned int’ [-Wformat=]
  648 |  dev_info(&bp->pdev->dev, "utc_offset: %d  valid:%d  leap_valid:%d\n",
      |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:19:22: note: in definition of macro ‘dev_fmt’
   19 | #define dev_fmt(fmt) fmt
      |                      ^~~
drivers/ptp/ptp_ocp.c:648:2: note: in expansion of macro ‘dev_info’
  648 |  dev_info(&bp->pdev->dev, "utc_offset: %d  valid:%d  leap_valid:%d\n",
      |  ^~~~~~~~
drivers/ptp/ptp_ocp.c:648:41: note: format string is defined here
  648 |  dev_info(&bp->pdev->dev, "utc_offset: %d  valid:%d  leap_valid:%d\n",
      |                                        ~^
      |                                         |
      |                                         int
      |                                        %ld

  reply	other threads:[~2021-08-17 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 12:24 Andy Shevchenko
2021-08-17 13:48 ` Jakub Kicinski [this message]
2021-08-17 16:46   ` Andy Shevchenko

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=20210817064814.13c57002@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=jonathan.lemon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --subject='Re: [PATCH v2 net-next 1/1] ptp_ocp: use bits.h macros for all masks' \
    /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

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).