netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: alexandru.tachici@analog.com, andrew@lunn.ch,
	davem@davemloft.net, devicetree@vger.kernel.org,
	hkallweit1@gmail.com, linux-kernel@vger.kernel.org,
	linux@armlinux.org.uk, netdev@vger.kernel.org,
	robh+dt@kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v5 0/7] net: phy: adin1100: Add initial support for ADIN1100 industrial PHY
Date: Thu, 7 Apr 2022 14:05:17 +0200	[thread overview]
Message-ID: <20220407120347.GA25348@pengutronix.de> (raw)
In-Reply-To: <20220324160041.0d775df8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Thu, Mar 24, 2022 at 04:00:41PM -0700, Jakub Kicinski wrote:
> On Thu, 24 Mar 2022 13:26:13 +0200 alexandru.tachici@analog.com wrote:
> > The ADIN1100 is a low power single port 10BASE-T1L transceiver designed for
> > industrial Ethernet applications and is compliant with the IEEE 802.3cg
> > Ethernet standard for long reach 10 Mb/s Single Pair Ethernet.
> 
> # Form letter - net-next is closed
> 
> We have already sent the networking pull request for 5.18
> and therefore net-next is closed for new drivers, features,
> code refactoring and optimizations. We are currently accepting
> bug fixes only.
> 
> Please repost when net-next reopens after 5.18-rc1 is cut.
> 
> RFC patches sent for review only are obviously welcome at any time.

Hi Alexandru net-next is open now, you can rebase and resend this
patches.

Regards,
Oleksij
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      reply	other threads:[~2022-04-07 12:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 11:26 [PATCH v5 0/7] net: phy: adin1100: Add initial support for ADIN1100 industrial PHY alexandru.tachici
2022-03-24 11:26 ` [PATCH v5 1/7] ethtool: Add 10base-T1L link mode entry alexandru.tachici
2022-03-24 11:26 ` [PATCH v5 2/7] net: phy: Add 10-BaseT1L registers alexandru.tachici
2022-03-24 11:26 ` [PATCH v5 3/7] net: phy: Add BaseT1 auto-negotiation registers alexandru.tachici
2022-03-24 11:26 ` [PATCH v5 4/7] net: phy: Add 10BASE-T1L support in phy-c45 alexandru.tachici
2022-03-24 11:26 ` [PATCH v5 5/7] net: phy: adin1100: Add initial support for ADIN1100 industrial PHY alexandru.tachici
2022-04-10  5:11   ` Ramon Fried
2022-04-10  5:12     ` Ramon Fried
2022-04-12  0:17     ` Zhou Furong
2022-03-24 11:26 ` [PATCH v5 6/7] net: phy: adin1100: Add SQI support alexandru.tachici
2022-03-24 11:26 ` [PATCH v5 7/7] dt-bindings: net: phy: Add 10-baseT1L 2.4 Vpp alexandru.tachici
2022-03-24 23:00 ` [PATCH v5 0/7] net: phy: adin1100: Add initial support for ADIN1100 industrial PHY Jakub Kicinski
2022-04-07 12:05   ` Oleksij Rempel [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=20220407120347.GA25348@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=alexandru.tachici@analog.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.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).