From: "Gan, Yi Fang" <yi.fang.gan@intel.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andrew Halaney" <ahalaney@redhat.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"John Stultz" <jstultz@google.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Gan Yi Fang" <yi.fang.gan@intel.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Russell King" <linux@armlinux.org.uk>,
"Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Marek Behún" <kabel@kernel.org>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Looi Hong Aun <hong.aun.looi@intel.com>,
Voon Weifeng <weifeng.voon@intel.com>,
Song Yoong Siang <yoong.siang.song@intel.com>,
Lai Peter Jun Ann <peter.jun.ann.lai@intel.com>,
Choong Yong Liang <yong.liang.choong@intel.com>
Subject: [PATCH net v2 0/2] Fix phylink unloadable issue
Date: Thu, 21 Dec 2023 16:51:07 +0800 [thread overview]
Message-ID: <20231221085109.2830794-1-yi.fang.gan@intel.com> (raw)
Add module_exit_stub() for phylink module.
Changes since v1:
- Introduce a helper macro for module_exit() boilerplate
This series is the combination of following:
v1 with empty phylink_exit():
https://lore.kernel.org/all/20231127101603.807593-1-yi.fang.gan@intel.com/
v1 of module_exit_stub():
https://lore.kernel.org/all/20231212094352.2263283-1-yi.fang.gan@intel.com/
Gan, Yi Fang (2):
driver.h: add helper macro for module_exit() boilerplate
net: phylink: Add module_exit_stub()
drivers/net/phy/phylink.c | 1 +
include/linux/device/driver.h | 14 ++++++++++++++
2 files changed, 15 insertions(+)
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-12-21 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 8:51 Gan, Yi Fang [this message]
2023-12-21 8:51 ` [PATCH net v2 1/2] driver.h: add helper macro for module_exit() boilerplate Gan, Yi Fang
2023-12-21 8:51 ` [PATCH net v2 2/2] net: phylink: Add module_exit_stub() Gan, Yi Fang
2023-12-21 9:22 ` Andrew Lunn
2024-01-04 9:45 ` Gan, Yi Fang
2024-01-04 13:00 ` Andrew Lunn
2023-12-21 9:11 ` [PATCH net v2 0/2] Fix phylink unloadable issue Greg Kroah-Hartman
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=20231221085109.2830794-1-yi.fang.gan@intel.com \
--to=yi.fang.gan@intel.com \
--cc=ahalaney@redhat.com \
--cc=andrew@lunn.ch \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=hong.aun.looi@intel.com \
--cc=javierm@redhat.com \
--cc=jstultz@google.com \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter.jun.ann.lai@intel.com \
--cc=rafael@kernel.org \
--cc=weifeng.voon@intel.com \
--cc=yong.liang.choong@intel.com \
--cc=yoong.siang.song@intel.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