From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Gan, Yi Fang" <yi.fang.gan@intel.com>
Cc: "Andrew Halaney" <ahalaney@redhat.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"John Stultz" <jstultz@google.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"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,
"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: Re: [PATCH net v2 0/2] Fix phylink unloadable issue
Date: Thu, 21 Dec 2023 10:11:04 +0100 [thread overview]
Message-ID: <2023122141-smuggling-confidant-d1d8@gregkh> (raw)
In-Reply-To: <20231221085109.2830794-1-yi.fang.gan@intel.com>
On Thu, Dec 21, 2023 at 04:51:07PM +0800, Gan, Yi Fang wrote:
> 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/
As I said before, no, this isn't ok. Why just resubmit a patch when
it's already been rejected?
This patch series should NOT be accepted as-is, you know this!
Also, you are not following the documented and REQUIRED rules for Intel
developers to be submitting kernel patches, so on that reason alone
these need to be rejected.
Please work with the Intel internel developers to do this correctly if
you wish to submit this again in the future.
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-12-21 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 8:51 [PATCH net v2 0/2] Fix phylink unloadable issue Gan, Yi Fang
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 ` Greg Kroah-Hartman [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=2023122141-smuggling-confidant-d1d8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ahalaney@redhat.com \
--cc=andrew@lunn.ch \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=yi.fang.gan@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