From: patchwork-bot+netdevbpf@kernel.org
To: Lucero@ci.codeaurora.org, Palau@ci.codeaurora.org,
Alejandro <alejandro.lucero-palau@amd.com>
Cc: netdev@vger.kernel.org, linux-net-drivers@amd.com,
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
Subject: Re: [PATCH v4 net-next] sfc: fix builds without CONFIG_RTC_LIB
Date: Tue, 21 Feb 2023 00:50:20 +0000 [thread overview]
Message-ID: <167694062019.10450.8199913841986761865.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230220110133.29645-1-alejandro.lucero-palau@amd.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 20 Feb 2023 11:01:33 +0000 you wrote:
> From: Alejandro Lucero <alejandro.lucero-palau@amd.com>
>
> Add an embarrassingly missed semicolon plus and embarrassingly missed
> parenthesis breaking kernel building when CONFIG_RTC_LIB is not set
> like the one reported with ia64 config.
>
> 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>
>
> [...]
Here is the summary with links:
- [v4,net-next] sfc: fix builds without CONFIG_RTC_LIB
https://git.kernel.org/netdev/net-next/c/5f22c3b6215d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-21 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 11:01 [PATCH v4 net-next] sfc: fix builds without CONFIG_RTC_LIB alejandro.lucero-palau
2023-02-21 0:50 ` patchwork-bot+netdevbpf [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=167694062019.10450.8199913841986761865.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Lucero@ci.codeaurora.org \
--cc=Palau@ci.codeaurora.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.