All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, Madalin Bucur <madalin.bucur@nxp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] net: fman: Various cleanups
Date: Tue, 31 May 2022 21:36:53 -0700	[thread overview]
Message-ID: <20220531213653.4f9b2b17@kernel.org> (raw)
In-Reply-To: <20220531195851.1592220-1-sean.anderson@seco.com>

On Tue, 31 May 2022 15:58:46 -0400 Sean Anderson wrote:
> This series performs a variety of cleanups for dpaa/fman, with the aim
> of reducing unused flexibility. I've tested this on layerscape, but I
> don't have any PPC platforms to test with (nor do I have access to the
> dtsec errata).

# Form letter - net-next is closed

We have already sent the networking pull request for 5.19
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.19-rc1 is cut.

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

  parent reply	other threads:[~2022-06-01  4:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 19:58 [PATCH 0/4] net: fman: Various cleanups Sean Anderson
2022-05-31 19:58 ` [PATCH 1/4] net: fman: Convert to SPDX identifiers Sean Anderson
2022-05-31 19:58 ` [PATCH 2/4] net: fman: Don't pass comm_mode to enable/disable Sean Anderson
2022-05-31 19:58 ` [PATCH 3/4] net: fman: Store en/disable in mac_device instead of mac_priv_s Sean Anderson
2022-05-31 19:58 ` [PATCH 4/4] net: fman: dtsec: Always gracefully stop/start Sean Anderson
2022-06-01  4:36 ` Jakub Kicinski [this message]
2022-06-07 14:25 ` [PATCH 0/4] net: fman: Various cleanups Camelia Alexandra Groza

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=20220531213653.4f9b2b17@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madalin.bucur@nxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=sean.anderson@seco.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 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.