All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Sean Anderson <seanga2@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Simon Horman <simon.horman@corigine.com>,
	debian-sparc@lists.debian.org, rescue@sunhelp.org,
	sparc@gentoo.org
Subject: Re: [PATCH net-next v2 0/9] net: sunhme: Probe/IRQ cleanups
Date: Mon, 13 Mar 2023 17:27:38 -0700	[thread overview]
Message-ID: <20230313172738.3508810f@kernel.org> (raw)
In-Reply-To: <20230311181905.3593904-1-seanga2@gmail.com>

On Sat, 11 Mar 2023 13:18:56 -0500 Sean Anderson wrote:
> 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...

Doesn't apply to net-next, please note we're using the branch called
*main* now.

  parent reply	other threads:[~2023-03-14  0:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 18:18 [PATCH net-next v2 0/9] net: sunhme: Probe/IRQ cleanups Sean Anderson
2023-03-11 18:18 ` [PATCH net-next v2 1/9] net: sunhme: Just restart autonegotiation if we can't bring the link up Sean Anderson
2023-03-11 18:18 ` [PATCH net-next v2 2/9] net: sunhme: Remove residual polling code Sean Anderson
2023-03-11 18:18 ` [PATCH net-next v2 3/9] net: sunhme: Unify IRQ requesting Sean Anderson
2023-03-11 18:19 ` [PATCH net-next v2 4/9] net: sunhme: Alphabetize includes Sean Anderson
2023-03-11 18:19 ` [PATCH net-next v2 5/9] net: sunhme: Switch SBUS to devres Sean Anderson
2023-03-11 18:19 ` [PATCH net-next v2 6/9] net: sunhme: Consolidate mac address initialization Sean Anderson
2023-03-11 18:19 ` [PATCH net-next v2 7/9] net: sunhme: Clean up mac address init Sean Anderson
2023-03-11 18:19 ` [PATCH net-next v2 8/9] net: sunhme: Inline error returns Sean Anderson
2023-03-11 18:19 ` [PATCH net-next v2 9/9] net: sunhme: Consolidate common probe tasks Sean Anderson
2023-03-14  0:27 ` Jakub Kicinski [this message]
2023-03-14  0:36   ` [PATCH net-next v2 0/9] net: sunhme: Probe/IRQ cleanups 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=20230313172738.3508810f@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=debian-sparc@lists.debian.org \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rescue@sunhelp.org \
    --cc=seanga2@gmail.com \
    --cc=simon.horman@corigine.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.