From: Jakub Kicinski <kuba@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, jacob.e.keller@intel.com,
horms@kernel.org, sd@queasysnail.net, chunkeey@gmail.com
Subject: Re: [PATCHv2 net-next 00/18] ibm: emac: more cleanups
Date: Wed, 2 Oct 2024 05:35:05 -0700 [thread overview]
Message-ID: <20241002053505.324c6636@kernel.org> (raw)
In-Reply-To: <20241001205844.306821-1-rosenp@gmail.com>
On Tue, 1 Oct 2024 13:58:26 -0700 Rosen Penev wrote:
> Added devm for the submodules and removed custom init/exit functions as
> EPROBE_DEFER is handled now.
>
> v2: fixed build errors. Also added extra commits to clean the driver up
> further.
Please include info on how this was tested
--
pw-bot: cr
prev parent reply other threads:[~2024-10-02 12:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 20:58 [PATCHv2 net-next 00/18] ibm: emac: more cleanups Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 01/18] net: ibm: emac: use netif_receive_skb_list Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 02/18] net: ibm: emac: remove custom init/exit functions Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 03/18] net: ibm: emac: use module_platform_driver for modules Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 04/18] net: ibm: emac: use devm_platform_ioremap_resource Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 05/18] net: ibm: emac: use platform_get_irq Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 06/18] net: ibm: emac: remove bootlist support Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 07/18] net: ibm: emac: tah: use devm for kzalloc Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 08/18] net: ibm: emac: tah: devm_platform_get_resources Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 09/18] net: ibm: emac: rgmii: use devm for kzalloc Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 10/18] net: ibm: emac: rgmii: devm_platform_get_resource Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 11/18] net: ibm: emac: zmii: use devm for kzalloc Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 12/18] net: ibm: emac: zmii: devm_platform_get_resource Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 13/18] net: ibm: emac: mal: use devm for kzalloc Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 14/18] net: ibm: emac: mal: use devm for request_irq Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 15/18] net: ibm: emac: mal: move irq maps down Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 16/18] net: ibm: emac: mal: move alloc_netdev_dummy down Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 17/18] net: ibm: emac: add dcr_unmap to _remove Rosen Penev
2024-10-01 20:58 ` [PATCHv2 net-next 18/18] net: ibm: emac: mal: move dcr map down Rosen Penev
2024-10-02 12:35 ` Jakub Kicinski [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=20241002053505.324c6636@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rosenp@gmail.com \
--cc=sd@queasysnail.net \
/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).