From: David Miller <davem@davemloft.net>
To: irusskikh@marvell.com
Cc: netdev@vger.kernel.org, aelior@marvell.com,
mkalderon@marvell.com, dbolotin@marvell.com, kuba@kernel.org
Subject: Re: [PATCH v2 net-next 00/11] net: qed/qede: critical hw error handling
Date: Thu, 14 May 2020 13:22:36 -0700 (PDT) [thread overview]
Message-ID: <20200514.132236.1465846961453548902.davem@davemloft.net> (raw)
In-Reply-To: <20200514.130952.794606246311304590.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Thu, 14 May 2020 13:09:52 -0700 (PDT)
> Actually, I had to revert, please fix these warnings (with gcc-10.1.1 on Fedora)_:
>
> drivers/net/ethernet/qlogic/qed/qed_dev.c: In function ‘qed_llh_add_mac_filter’:
> ./include/linux/printk.h:303:2: warning: ‘abs_ppfid’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> 303 | printk(KERN_NOTICE pr_fmt(fmt), ##__VA_ARGS__)
> | ^~~~~~
> drivers/net/ethernet/qlogic/qed/qed_dev.c:983:17: note: ‘abs_ppfid’ was declared here
> 983 | u8 filter_idx, abs_ppfid;
> | ^~~~~~~~~
Hmm, this seems to actually be an existing warning, sorry.
I'll reapply this.
prev parent reply other threads:[~2020-05-14 20:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 9:57 [PATCH v2 net-next 00/11] net: qed/qede: critical hw error handling Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 01/11] net: qed: adding hw_err states and handling Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 02/11] net: qede: add hw err scheduled handler Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 03/11] net: qed: invoke err notify on critical areas Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 04/11] net: qed: critical err reporting to management firmware Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 05/11] net: qed: cleanup debug related declarations Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 06/11] net: qed: attention clearing properties Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 07/11] net: qede: optional hw recovery procedure Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 08/11] net: qede: Implement ndo_tx_timeout Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 09/11] net: qed: introduce critical fan failure handler Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 10/11] net: qed: introduce critical hardware error handler Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 11/11] net: qed: fix bad formatting Igor Russkikh
2020-05-14 19:06 ` [PATCH v2 net-next 00/11] net: qed/qede: critical hw error handling Jakub Kicinski
2020-05-14 19:40 ` [EXT] " Igor Russkikh
2020-05-14 20:02 ` Jakub Kicinski
2020-05-14 20:09 ` Igor Russkikh
2020-05-14 20:01 ` David Miller
2020-05-14 20:09 ` David Miller
2020-05-14 20:22 ` David Miller [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=20200514.132236.1465846961453548902.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aelior@marvell.com \
--cc=dbolotin@marvell.com \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=mkalderon@marvell.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).