public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: hikey9xx: Remove defined but unused macros
Date: Tue, 25 May 2021 18:24:02 +0200	[thread overview]
Message-ID: <YK0komOt7j8R9045@kroah.com> (raw)
In-Reply-To: <20210523172709.19181-1-fmdefrancesco@gmail.com>

On Sun, May 23, 2021 at 07:27:09PM +0200, Fabio M. De Francesco wrote:
> Removed defined but unused macros. Issue detected by GCC running with
> -Wunused-macro warning option set.
> 
> Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> ---
>  drivers/staging/hikey9xx/hisi-spmi-controller.c | 9 ---------
>  1 file changed, 9 deletions(-)
> 
> diff --git a/drivers/staging/hikey9xx/hisi-spmi-controller.c b/drivers/staging/hikey9xx/hisi-spmi-controller.c
> index 0d42bc65f39b..b64594e2a84b 100644
> --- a/drivers/staging/hikey9xx/hisi-spmi-controller.c
> +++ b/drivers/staging/hikey9xx/hisi-spmi-controller.c
> @@ -21,16 +21,10 @@
>  #define SPMI_APB_SPMI_CMD_BASE_ADDR			0x0100
>  
>  #define SPMI_APB_SPMI_WDATA0_BASE_ADDR			0x0104
> -#define SPMI_APB_SPMI_WDATA1_BASE_ADDR			0x0108
> -#define SPMI_APB_SPMI_WDATA2_BASE_ADDR			0x010c
> -#define SPMI_APB_SPMI_WDATA3_BASE_ADDR			0x0110
>  
>  #define SPMI_APB_SPMI_STATUS_BASE_ADDR			0x0200
>  
>  #define SPMI_APB_SPMI_RDATA0_BASE_ADDR			0x0204
> -#define SPMI_APB_SPMI_RDATA1_BASE_ADDR			0x0208
> -#define SPMI_APB_SPMI_RDATA2_BASE_ADDR			0x020c
> -#define SPMI_APB_SPMI_RDATA3_BASE_ADDR			0x0210
>  
>  #define SPMI_PER_DATAREG_BYTE				4
>  /*
> @@ -64,9 +58,6 @@ enum spmi_controller_cmd_op_code {
>  #define SPMI_APB_TRANS_DONE			BIT(0)
>  #define SPMI_APB_TRANS_FAIL			BIT(2)
>  
> -/* Command register fields */
> -#define SPMI_CONTROLLER_CMD_MAX_BYTE_COUNT	16
> -
>  /* Maximum number of support PMIC peripherals */
>  #define SPMI_CONTROLLER_TIMEOUT_US		1000
>  #define SPMI_CONTROLLER_MAX_TRANS_BYTES		16
> -- 
> 2.31.1
> 
> 

Leaving macros that are not used are fine to keep around, it documents
the hardware.

That's a pretty foolish gcc warning :(


thanks,

greg k-h

      reply	other threads:[~2021-05-25 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23 17:27 [PATCH] staging: hikey9xx: Remove defined but unused macros Fabio M. De Francesco
2021-05-25 16:24 ` Greg Kroah-Hartman [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=YK0komOt7j8R9045@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab+huawei@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