devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: andrei.tachici@stud.acs.upb.ro
Cc: linux-kernel@vger.kernel.org, andrew@lunn.ch,
	hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
	vegard.nossum@oracle.com, joel@jms.id.au, l.stelmach@samsung.com,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	devicetree@vger.kernel.org
Subject: Re: [net-next v3 0/3] net: ethernet: adi: Add ADIN1110 support
Date: Tue, 2 Aug 2022 12:29:49 -0700	[thread overview]
Message-ID: <20220802122949.7080822f@kernel.org> (raw)
In-Reply-To: <20220802155947.83060-1-andrei.tachici@stud.acs.upb.ro>

On Tue,  2 Aug 2022 18:59:44 +0300 andrei.tachici@stud.acs.upb.ro wrote:
> Subject: [net-next v3 0/3] net: ethernet: adi: Add ADIN1110 support

# Form letter - net-next is closed

The merge window for Linux 6.0 has started 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 6.0-rc1 is cut.

RFC patches sent for review only are obviously welcome at any time.

      parent reply	other threads:[~2022-08-02 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 15:59 [net-next v3 0/3] net: ethernet: adi: Add ADIN1110 support andrei.tachici
2022-08-02 15:59 ` [net-next v3 1/3] net: phy: adin1100: add PHY IDs of adin1110/adin2111 andrei.tachici
2022-08-02 15:59 ` [net-next v3 2/3] net: ethernet: adi: Add ADIN1110 support andrei.tachici
2022-08-02 15:59 ` [net-next v3 3/3] dt-bindings: net: adin1110: Add docs andrei.tachici
2022-08-02 19:35   ` Rob Herring
2022-08-03 20:40   ` Rob Herring
2022-08-02 19:29 ` 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=20220802122949.7080822f@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrei.tachici@stud.acs.upb.ro \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=joel@jms.id.au \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=l.stelmach@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@kernel.org \
    --cc=vegard.nossum@oracle.com \
    /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).