public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@kernel.org>
To: "Andreas Kühn" <andreas.kuehn@diekuehnen.com>
Cc: avifishman70@gmail.com, tmaimon77@gmail.com,
	tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
	benjaminfair@google.com, gregkh@linuxfoundation.org,
	openbmc@lists.ozlabs.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: chipidea: npcm: Fix coding style with clarification of data type
Date: Thu, 5 Sep 2024 15:46:30 +0800	[thread overview]
Message-ID: <20240905074630.GA325295@nchen-desktop> (raw)
In-Reply-To: <20240903132535.15554-1-andreas.kuehn@diekuehnen.com>

On 24-09-03 15:25:15, Andreas Kühn wrote:
> Fixed coding style issue: unsigned to unsigned int.
> 
> Signed-off-by: Andreas Kühn <andreas.kuehn@diekuehnen.com>

Acked-by: Peter Chen <peter.chen@kernel.org>


> ---
>  drivers/usb/chipidea/ci_hdrc_npcm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/chipidea/ci_hdrc_npcm.c b/drivers/usb/chipidea/ci_hdrc_npcm.c
> index c89c68f41ccc..3e5e05dbda89 100644
> --- a/drivers/usb/chipidea/ci_hdrc_npcm.c
> +++ b/drivers/usb/chipidea/ci_hdrc_npcm.c
> @@ -18,7 +18,7 @@ struct npcm_udc_data {
>  	struct ci_hdrc_platform_data pdata;
>  };
>  
> -static int npcm_udc_notify_event(struct ci_hdrc *ci, unsigned event)
> +static int npcm_udc_notify_event(struct ci_hdrc *ci, unsigned int event)
>  {
>  	struct device *dev = ci->dev->parent;
>  
> -- 
> 2.43.0
> 

      reply	other threads:[~2024-09-05  7:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 13:25 [PATCH] usb: chipidea: npcm: Fix coding style with clarification of data type Andreas Kühn
2024-09-05  7:46 ` Peter Chen [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=20240905074630.GA325295@nchen-desktop \
    --to=peter.chen@kernel.org \
    --cc=andreas.kuehn@diekuehnen.com \
    --cc=avifishman70@gmail.com \
    --cc=benjaminfair@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tali.perry1@gmail.com \
    --cc=tmaimon77@gmail.com \
    --cc=venture@google.com \
    --cc=yuenn@google.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