From: Jakub Kicinski <kuba@kernel.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-mips@vger.kernel.org, Jonas Gorski <jonas.gorski@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 5/6] net: cpmac: remove driver to prepare for platform removal
Date: Thu, 5 Oct 2023 07:16:34 -0700 [thread overview]
Message-ID: <20231005071634.581fa8c2@kernel.org> (raw)
In-Reply-To: <ZR7Dd8wy91+G2U3v@alpha.franken.de>
On Thu, 5 Oct 2023 16:08:55 +0200 Thomas Bogendoerfer wrote:
> On Fri, Sep 22, 2023 at 08:15:26AM +0200, Wolfram Sang wrote:
> > AR7 is going to be removed from the Kernel, so remove its networking
> > support in form of the cpmac driver. This allows us to remove the
> > platform because this driver includes a platform specific header.
> >
> > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> > ---
> > Changes since v1:
> > * added ack
> >
> > MAINTAINERS | 6 -
> > drivers/net/ethernet/ti/Kconfig | 9 +-
> > drivers/net/ethernet/ti/Makefile | 1 -
> > drivers/net/ethernet/ti/cpmac.c | 1251 ------------------------------
> > 4 files changed, 1 insertion(+), 1266 deletions(-)
> > delete mode 100644 drivers/net/ethernet/ti/cpmac.c
> > [..]
>
> is it ok for network people to route this patch via mips-next tree
> or do you want to apply to net-next ?
We have a ".remove callback should return void" conversion from Uwe
queued for the deleted driver (231ea972ccaf5b). The conflict will be
really trivial, but I guess no conflict beats trivial conflict so better
if we take it? :S
next prev parent reply other threads:[~2023-10-05 15:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 6:15 [PATCH v2 0/6] remove AR7 platform and associated drivers Wolfram Sang
2023-09-22 6:15 ` [PATCH v2 1/6] serial: 8250: remove AR7 support Wolfram Sang
2023-09-22 6:15 ` [PATCH v2 2/6] mtd: parsers: ar7: remove support Wolfram Sang
2023-09-22 14:39 ` Miquel Raynal
2023-09-22 17:55 ` Wolfram Sang
2023-09-22 18:35 ` Philippe Mathieu-Daudé
2023-09-25 7:11 ` Miquel Raynal
2023-09-28 7:10 ` Wolfram Sang
2023-10-02 9:39 ` Miquel Raynal
2023-09-22 6:15 ` [PATCH v2 3/6] vlynq: remove bus driver Wolfram Sang
2023-09-22 6:15 ` [PATCH v2 4/6] watchdog: ar7_wdt: remove driver to prepare for platform removal Wolfram Sang
2023-09-22 6:15 ` [PATCH net-next v2 5/6] net: cpmac: " Wolfram Sang
2023-10-05 14:08 ` Thomas Bogendoerfer
2023-10-05 14:16 ` Jakub Kicinski [this message]
2023-10-05 19:07 ` Thomas Bogendoerfer
2023-10-06 14:26 ` Jakub Kicinski
2023-09-22 6:15 ` [PATCH v2 6/6] MIPS: AR7: remove platform Wolfram Sang
2023-09-28 7:06 ` Wolfram Sang
2023-09-28 7:29 ` Thomas Bogendoerfer
2023-09-28 7:49 ` Wolfram Sang
2023-10-06 8:20 ` Thomas Bogendoerfer
2023-10-19 8:49 ` Thomas Bogendoerfer
2023-10-19 12:32 ` Wolfram Sang
2023-10-19 8:50 ` [PATCH v2 0/6] remove AR7 platform and associated drivers Thomas Bogendoerfer
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=20231005071634.581fa8c2@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tsbogend@alpha.franken.de \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).