From: Andrew Lunn <andrew@lunn.ch>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
jacob.e.keller@intel.com, horms@kernel.org, sd@queasysnail.net,
chunkeey@gmail.com
Subject: Re: [PATCH net-next 0/6] net: ibm: emac: some cleanups and devm
Date: Mon, 2 Sep 2024 22:00:17 +0200 [thread overview]
Message-ID: <b149c9cd-a76b-4fb8-b3ff-430afa8fdd77@lunn.ch> (raw)
In-Reply-To: <20240902181530.6852-1-rosenp@gmail.com>
On Mon, Sep 02, 2024 at 11:15:09AM -0700, Rosen Penev wrote:
> It's a very old driver with a lot of potential for cleaning up code to
> modern standards. This was a simple one dealing with mostly the probe
> function and adding some devm to it.
>
> All patches were tested on a Cisco Meraki MX60W. Boot and
> Shutdown/Reboot showed no warnings.
This is a 12 year old PowerPC system. Cool you found one. Looks like
OpenWRT still supports it.
Andrwq
next prev parent reply other threads:[~2024-09-02 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 18:15 Rosen Penev
2024-09-02 18:15 ` [PATCH 1/6] net: ibm: emac: use devm for alloc_etherdev Rosen Penev
2024-09-02 18:15 ` [PATCH 2/6] net: ibm: emac: manage emac_irq with devm Rosen Penev
2024-09-02 20:06 ` Andrew Lunn
2024-09-02 20:26 ` Rosen Penev
2024-09-02 20:39 ` Andrew Lunn
2024-09-02 18:15 ` [PATCH 3/6] net: ibm: emac: use devm for of_iomap Rosen Penev
2024-09-02 18:15 ` [PATCH 4/6] net: ibm: emac: remove mii_bus with devm Rosen Penev
2024-09-02 18:15 ` [PATCH 5/6] net: ibm: emac: use devm for register_netdev Rosen Penev
2024-09-02 18:15 ` [PATCH 6/6] net: ibm: emac: use netdev's phydev directly Rosen Penev
2024-09-02 20:00 ` Andrew Lunn [this message]
2024-09-02 20:20 ` [PATCH net-next 0/6] net: ibm: emac: some cleanups and devm Rosen Penev
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=b149c9cd-a76b-4fb8-b3ff-430afa8fdd77@lunn.ch \
--to=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=kuba@kernel.org \
--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
all inboxes | Powered by JetHome®