From: Greg KH <gregkh@linuxfoundation.org>
To: guoren@kernel.org
Cc: palmer@dabbelt.com, conor@kernel.org, geert+renesas@glider.be,
prabhakar.mahadev-lad.rj@bp.renesas.com,
yoshihiro.shimoda.uh@renesas.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>,
stable@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH V2] usb: gadget: udc: renesas_usb3: Fix compiler warning
Date: Mon, 3 Feb 2025 16:41:03 +0100 [thread overview]
Message-ID: <2025020324-siding-custodian-b21d@gregkh> (raw)
In-Reply-To: <20250122081231.47594-1-guoren@kernel.org>
On Wed, Jan 22, 2025 at 03:12:31AM -0500, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> drivers/usb/gadget/udc/renesas_usb3.c: In function 'renesas_usb3_probe':
> drivers/usb/gadget/udc/renesas_usb3.c:2638:73: warning: '%d'
> directive output may be truncated writing between 1 and 11 bytes into a
> region of size 6 [-Wformat-truncation=]
> 2638 | snprintf(usb3_ep->ep_name, sizeof(usb3_ep->ep_name), "ep%d", i);
> ^~~~~~~~~~~~~~~~~~~~~~~~ ^~ ^
>
> Fixes: 746bfe63bba3 ("usb: gadget: renesas_usb3: add support for Renesas
> USB3.0 peripheral controller")
Please don't wrap lines here.
> Cc: stable@vger.kernel.org
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202501201409.BIQPtkeB-lkp@intel.com/
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
No need to sign off twice on a commit, I'll just drop the last one as
that doesn't match the From: line here.
thanks,
greg k-h
prev parent reply other threads:[~2025-02-03 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 8:12 [PATCH V2] usb: gadget: udc: renesas_usb3: Fix compiler warning guoren
2025-01-22 8:58 ` Greg KH
2025-02-03 15:41 ` Greg KH [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=2025020324-siding-custodian-b21d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=conor@kernel.org \
--cc=geert+renesas@glider.be \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=palmer@dabbelt.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=stable@vger.kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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