From: Alexandra Winter <wintera@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Simon Horman <simon.horman@corigine.com>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Wenjia Zhang <wenjia@linux.ibm.com>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH] s390/net: lcs: fix build errors when FDDI is a loadable module
Date: Wed, 28 Jun 2023 15:41:26 +0200 [thread overview]
Message-ID: <a05a7c3a-0f2f-c3be-3630-6774a26b994f@linux.ibm.com> (raw)
In-Reply-To: <510b6216-35e5-5ea1-525f-5fab35b901e0@infradead.org>
On 28.06.23 07:06, Randy Dunlap wrote:
> Hi Alexandra, Simon, others,
>
> Here is v2 of this patch. I will send it formally after the merge window closes.
>
> Thanks for all of your help.
> ---
Thank you for the patch, Randy.
As suggested by Christian Bornträger, I did some research, whether the FDDI part of the LCS driver
could be removed. And actually there is no s390 machine above the minimum architecture level that
can have an FDDI interface.
I will send a patch to remove the FDDI option from the lcs driver.
I apologize that I was not aware of that earlier. And thank you again for pointing out the issue
with FDDI as a module.
Alexandra
next prev parent reply other threads:[~2023-06-28 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 21:37 [PATCH] s390/net: lcs: fix build errors when FDDI is a loadable module Randy Dunlap
2023-06-22 7:15 ` Alexandra Winter
2023-06-22 7:53 ` Simon Horman
2023-06-22 12:16 ` Alexandra Winter
2023-06-22 12:33 ` Christian Borntraeger
2023-06-28 2:53 ` Randy Dunlap
2023-06-28 5:06 ` Randy Dunlap
2023-06-28 13:41 ` Alexandra Winter [this message]
2023-06-28 15:29 ` Randy Dunlap
2023-06-22 15:36 ` 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=a05a7c3a-0f2f-c3be-3630-6774a26b994f@linux.ibm.com \
--to=wintera@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=simon.horman@corigine.com \
--cc=svens@linux.ibm.com \
--cc=wenjia@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox