From: <alejandro.lucero-palau@amd.com>
To: <netdev@vger.kernel.org>, <linux-net-drivers@amd.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>,
<edumazet@google.com>, <habetsm.xilinx@gmail.com>,
<ecree.xilinx@gmail.com>, <linux-doc@vger.kernel.org>,
<corbet@lwn.net>, <jiri@nvidia.com>,
"Alejandro Lucero" <alejandro.lucero-palau@amd.com>
Subject: [PATCH] sfc: fix builds without CONFIG_RTC_LIB
Date: Fri, 17 Feb 2023 10:22:36 +0000 [thread overview]
Message-ID: <20230217102236.48789-1-alejandro.lucero-palau@amd.com> (raw)
From: Alejandro Lucero <alejandro.lucero-palau@amd.com>
Adding an embarrasing missing semicolon precluding kernel building
in ia64 configs.
Reported-by: kernel test robot <lkp@intel.com>
Link: https://lore.kernel.org/oe-kbuild-all/202302170047.EjCPizu3-lkp@intel.com/
Fixes: 14743ddd2495 ("sfc: add devlink info support for ef100")
Signed-off-by: Alejandro Lucero <alejandro.lucero-palau@amd.com>
---
drivers/net/ethernet/sfc/efx_devlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/sfc/efx_devlink.c b/drivers/net/ethernet/sfc/efx_devlink.c
index d2eb6712ba35..3eb355fd4282 100644
--- a/drivers/net/ethernet/sfc/efx_devlink.c
+++ b/drivers/net/ethernet/sfc/efx_devlink.c
@@ -323,7 +323,7 @@ static void efx_devlink_info_running_v2(struct efx_nic *efx,
GET_VERSION_V2_OUT_SUCFW_BUILD_DATE);
rtc_time64_to_tm(tstamp, &build_date);
#else
- memset(&build_date, 0, sizeof(build_date)
+ memset(&build_date, 0, sizeof(build_date);
#endif
build_id = MCDI_DWORD(outbuf, GET_VERSION_V2_OUT_SUCFW_CHIP_ID);
--
2.17.1
next reply other threads:[~2023-02-17 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 10:22 alejandro.lucero-palau [this message]
2023-02-17 14:47 ` [PATCH] sfc: fix builds without CONFIG_RTC_LIB Alexander Lobakin
2023-02-17 15:20 ` Lucero Palau, Alejandro
2023-02-17 15:30 ` Lucero Palau, Alejandro
2023-02-17 16:46 ` Paolo Abeni
2023-02-23 15:29 ` Alexander Lobakin
2023-02-17 15:13 ` Manank Patel
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=20230217102236.48789-1-alejandro.lucero-palau@amd.com \
--to=alejandro.lucero-palau@amd.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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