From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, wintera@linux.ibm.com,
wenjia@linux.ibm.com, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com
Subject: Re: [PATCH] s390/net: lcs: use IS_ENABLED() for kconfig detection
Date: Fri, 16 Jun 2023 08:10:20 +0000 [thread overview]
Message-ID: <168690302072.8823.785077843270614259.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230615222152.13250-1-rdunlap@infradead.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 15 Jun 2023 15:21:52 -0700 you wrote:
> When CONFIG_ETHERNET=m or CONFIG_FDDI=m, lcs.s has build errors or
> warnings:
>
> ../drivers/s390/net/lcs.c:40:2: error: #error Cannot compile lcs.c without some net devices switched on.
> 40 | #error Cannot compile lcs.c without some net devices switched on.
> ../drivers/s390/net/lcs.c: In function 'lcs_startlan_auto':
> ../drivers/s390/net/lcs.c:1601:13: warning: unused variable 'rc' [-Wunused-variable]
> 1601 | int rc;
>
> [...]
Here is the summary with links:
- s390/net: lcs: use IS_ENABLED() for kconfig detection
https://git.kernel.org/netdev/net-next/c/128272336120
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-06-16 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 22:21 [PATCH] s390/net: lcs: use IS_ENABLED() for kconfig detection Randy Dunlap
2023-06-16 8:10 ` patchwork-bot+netdevbpf [this message]
2023-06-19 10:04 ` Alexandra Winter
2023-06-19 15:18 ` Randy Dunlap
2023-06-21 2:35 ` Randy Dunlap
2023-06-21 15:53 ` Simon Horman
2023-06-21 18:08 ` Randy Dunlap
2023-06-21 19:37 ` Simon Horman
2023-06-21 21:19 ` Randy Dunlap
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=168690302072.8823.785077843270614259.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=svens@linux.ibm.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.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.