From: Test Bot <zgrieee@gmail.com>
To: peppe.cavallaro@st.com, linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, linux@armlinux.org.uk,
linux-stm32@st-md-mailman.stormreply.com, bpf@vger.kernel.org,
ozgurk@ieee.org
Subject: ERROR: drivers: net: ethernet: stmicro: stmmac: stmmac_main.c
Date: Thu, 12 May 2022 23:48:59 +0400 [thread overview]
Message-ID: <CAOFRbGnQ1P4q+egG+K=BcZL4bwaAdtp7hQ1nh9TYJyky0j3WDw@mail.gmail.com> (raw)
Hi,
I automatically test (RC) kernel and caught ERROR word.
Please ignore, if its unimportant.
Kernel: 5.18-rc6
Arch: x86_64 (SMP)
Compiler: 7.5.0 (gcc)
FIle: drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
Codebase Block:
static int stmmac_request_irq_multi_msi(struct net_device *dev)
{
struct stmmac_priv *priv = netdev_priv(dev);
enum request_irq_err irq_err;
cpumask_t cpu_mask;
int irq_idx = 0;
char *int_name;
int ret;
int i;
int_name = priv->int_name_mac;
sprintf(int_name, "%s:%s", dev->name, "mac");
ret = request_irq(dev->irq, stmmac_mac_interrupt,
0, int_name, dev);
if (unlikely(ret < 0)) {
netdev_err(priv->dev,
"%s: alloc mac MSI %d (error: %d)\n",
__func__, dev->irq, ret);
irq_err = REQ_IRQ_ERR_MAC;
goto irq_error;
}
if (priv->wol_irq > 0 && priv->wol_irq != dev->irq) {
int_name = priv->int_name_wol;
sprintf(int_name, "%s:%s", dev->name, "wol");
ret = request_irq(priv->wol_irq,
stmmac_mac_interrupt,
0, int_name, dev);
if (unlikely(ret < 0)) {
netdev_err(priv->dev,
"%s: alloc wol MSI %d (error: %d)\n",
__func__, priv->wol_irq, ret);
irq_err = REQ_IRQ_ERR_WOL;
goto irq_error;
}
}
Compiler Log:
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c: In function
‘stmmac_request_irq_multi_msi’:
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c:3562:1: warning: the
frame size of 1040 bytes is larger than 1024 bytes
[-Wframe-larger-than=]
next reply other threads:[~2022-05-12 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 19:48 Test Bot [this message]
2022-05-12 20:06 ` ERROR: drivers: net: ethernet: stmicro: stmmac: stmmac_main.c Ozgur
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='CAOFRbGnQ1P4q+egG+K=BcZL4bwaAdtp7hQ1nh9TYJyky0j3WDw@mail.gmail.com' \
--to=zgrieee@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=ozgurk@ieee.org \
--cc=peppe.cavallaro@st.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;
as well as URLs for NNTP newsgroup(s).