From: Sean Anderson <seanga2@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sean Anderson <seanga2@gmail.com>,
debian-sparc@lists.debian.org, rescue@sunhelp.org,
sparc@gentoo.org
Subject: [RFC PATCH net-next 0/7] net: sunhme: Probe/IRQ cleanups
Date: Wed, 22 Feb 2023 16:03:48 -0500 [thread overview]
Message-ID: <20230222210355.2741485-1-seanga2@gmail.com> (raw)
Well, I've had these patches kicking around in my tree since last October, so I
guess I had better get around to posting them. This series is mainly a
cleanup/consolidation of the probe process, with some interrupt changes as well.
Some of these changes are SBUS- (AKA SPARC-) specific, so this should really get
some testing there as well to ensure nothing breaks. I've CC'd a few SPARC
mailing lists in hopes that someone there can try this out. I also have an SBUS
card I ordered by mistake if anyone has a SPARC computer but lacks this card.
I had originally planned on adding phylib support to this driver in the hopes of
being able to use real phy drivers, but I don't think I'm going to end up doing
that. I wanted to be able to use an external (homegrown) phy, but as it turns
out you can't buy MII cables in $CURRENTYEAR for under $250 a pop, and even if
you could get them you can't buy the connectors either. Oh well...
This series is not actually RFC, but I don't want to forget to post this in
another month.
Sean Anderson (7):
net: sunhme: Just restart autonegotiation if we can't bring the link
up
net: sunhme: Remove residual polling code
net: sunhme: Unify IRQ requesting
net: sunhme: Alphabetize includes
net: sunhme: Switch SBUS to devres
net: sunhme: Consolidate mac address initialization
net: sunhme: Consolidate common probe tasks
drivers/net/ethernet/sun/sunhme.c | 891 ++++++++++--------------------
drivers/net/ethernet/sun/sunhme.h | 6 +-
2 files changed, 288 insertions(+), 609 deletions(-)
--
2.37.1
next reply other threads:[~2023-02-22 21:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 21:03 Sean Anderson [this message]
2023-02-22 21:03 ` [RFC PATCH net-next 1/7] net: sunhme: Just restart autonegotiation if we can't bring the link up Sean Anderson
2023-02-25 16:56 ` Simon Horman
2023-02-25 18:59 ` Sean Anderson
2023-02-22 21:03 ` [RFC PATCH net-next 2/7] net: sunhme: Remove residual polling code Sean Anderson
2023-02-22 21:03 ` [RFC PATCH net-next 3/7] net: sunhme: Unify IRQ requesting Sean Anderson
2023-02-22 21:03 ` [RFC PATCH net-next 4/7] net: sunhme: Alphabetize includes Sean Anderson
2023-02-25 21:07 ` Simon Horman
2023-02-22 21:03 ` [RFC PATCH net-next 5/7] net: sunhme: Switch SBUS to devres Sean Anderson
2023-02-22 21:03 ` [RFC PATCH net-next 6/7] net: sunhme: Consolidate mac address initialization Sean Anderson
2023-02-25 18:39 ` Simon Horman
2023-02-25 18:59 ` Sean Anderson
2023-02-25 20:27 ` Simon Horman
2023-02-22 21:03 ` [RFC PATCH net-next 7/7] net: sunhme: Consolidate common probe tasks Sean Anderson
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=20230222210355.2741485-1-seanga2@gmail.com \
--to=seanga2@gmail.com \
--cc=davem@davemloft.net \
--cc=debian-sparc@lists.debian.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rescue@sunhelp.org \
--cc=sparc@gentoo.org \
/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).