From: <akiyano@amazon.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Arthur Kiyanovski <akiyano@amazon.com>, <dwmw@amazon.com>,
<zorik@amazon.com>, <matua@amazon.com>, <saeedb@amazon.com>,
<msw@amazon.com>, <aliguori@amazon.com>, <nafea@amazon.com>,
<gtzalik@amazon.com>, <netanel@amazon.com>, <alisaidi@amazon.com>,
<benh@amazon.com>, <ndagan@amazon.com>, <shayagr@amazon.com>,
<sameehj@amazon.com>
Subject: [PATCH V3 net-next 3/8] net: ena: cosmetic: satisfy gcc warning
Date: Tue, 21 Jul 2020 16:38:06 +0300 [thread overview]
Message-ID: <1595338691-3130-4-git-send-email-akiyano@amazon.com> (raw)
In-Reply-To: <1595338691-3130-1-git-send-email-akiyano@amazon.com>
From: Arthur Kiyanovski <akiyano@amazon.com>
gcc 4.8 reports a warning when initializing with = {0}.
Dropping the "0" from the braces fixes the issue.
This fix is not ANSI compatible but is allowed by gcc.
Signed-off-by: Sameeh Jubran <sameehj@amazon.com>
Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
---
drivers/net/ethernet/amazon/ena/ena_netdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/amazon/ena/ena_netdev.c b/drivers/net/ethernet/amazon/ena/ena_netdev.c
index e453542c9e94..d3d2e3934237 100644
--- a/drivers/net/ethernet/amazon/ena/ena_netdev.c
+++ b/drivers/net/ethernet/amazon/ena/ena_netdev.c
@@ -307,7 +307,7 @@ static int ena_xdp_xmit_buff(struct net_device *dev,
struct ena_rx_buffer *rx_info)
{
struct ena_adapter *adapter = netdev_priv(dev);
- struct ena_com_tx_ctx ena_tx_ctx = {0};
+ struct ena_com_tx_ctx ena_tx_ctx = {};
struct ena_tx_buffer *tx_info;
struct ena_ring *xdp_ring;
u16 next_to_use, req_id;
--
2.23.3
next prev parent reply other threads:[~2020-07-21 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 13:38 [PATCH V3 net-next 0/8] ENA driver new features akiyano
2020-07-21 13:38 ` [PATCH V3 net-next 1/8] net: ena: avoid unnecessary rearming of interrupt vector when busy-polling akiyano
2020-07-21 13:38 ` [PATCH V3 net-next 2/8] net: ena: add reserved PCI device ID akiyano
2020-07-21 13:38 ` akiyano [this message]
2020-07-21 13:38 ` [PATCH V3 net-next 4/8] net: ena: cosmetic: change ena_com_stats_admin stats to u64 akiyano
2020-07-21 13:38 ` [PATCH V3 net-next 5/8] net: ena: add support for traffic mirroring akiyano
2020-07-21 13:38 ` [PATCH V3 net-next 6/8] net: ena: enable support of rss hash key and function changes akiyano
2020-07-21 13:38 ` [PATCH V3 net-next 7/8] net: ena: move llq configuration from ena_probe to ena_device_init() akiyano
2020-07-21 13:38 ` [PATCH V3 net-next 8/8] net: ena: support new LLQ acceleration mode akiyano
2020-07-21 19:26 ` [PATCH V3 net-next 0/8] ENA driver new features Jakub Kicinski
2020-07-21 22:59 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2020-07-16 18:10 akiyano
2020-07-16 18:10 ` [PATCH V3 net-next 3/8] net: ena: cosmetic: satisfy gcc warning akiyano
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=1595338691-3130-4-git-send-email-akiyano@amazon.com \
--to=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.com \
--cc=gtzalik@amazon.com \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=saeedb@amazon.com \
--cc=sameehj@amazon.com \
--cc=shayagr@amazon.com \
--cc=zorik@amazon.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).