linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Mihai Moldovan <ionic@ionic.de>
Cc: linux-arm-msm@vger.kernel.org,
	Manivannan Sadhasivam <mani@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Willem de Bruijn <willemb@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Simon Horman <horms@kernel.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v4 00/11] QRTR Multi-endpoint support
Date: Wed, 30 Jul 2025 17:57:12 -0700	[thread overview]
Message-ID: <20250730175712.76c3e2a7@kernel.org> (raw)
In-Reply-To: <cover.1753720934.git.ionic@ionic.de>

On Mon, 28 Jul 2025 18:45:17 +0200 Mihai Moldovan wrote:
> I am incredibly thankful for Denis's work on this. To get this back on
> track and to eventually get it merged, with his permission, I'm
> resubmitting his patch set with issues in the previous review rounds
> resolved. This feature is a prerequisite for my work on ath1{1,2}k to
> allow using multiple devices in one computer.

## Form letter - net-next-closed

We have already submitted our pull request with net-next material for v6.17,
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 Aug 11th.

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

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
-- 
pw-bot: defer
pv-bot: closed


  parent reply	other threads:[~2025-07-31  0:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 16:45 [PATCH v4 00/11] QRTR Multi-endpoint support Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 01/11] net: qrtr: ns: validate msglen before ctrl_pkt use Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 02/11] net: qrtr: allocate and track endpoint ids Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 03/11] net: qrtr: fit node ID + port number combination into unsigned long Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 04/11] net: qrtr: support identical node ids Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 05/11] net: qrtr: Report sender endpoint in aux data Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 06/11] net: qrtr: Report endpoint for locally generated messages Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 07/11] net: qrtr: Allow sendmsg to target an endpoint Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 08/11] net: qrtr: allow socket endpoint binding Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 09/11] net: qrtr: Drop remote {NEW|DEL}_LOOKUP messages Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 10/11] net: qrtr: ns: support multiple endpoints Mihai Moldovan
2025-07-28 16:45 ` [PATCH v4 11/11] net: qrtr: mhi: Report endpoint id in sysfs Mihai Moldovan
2025-07-31  0:57 ` Jakub Kicinski [this message]
2025-07-31  5:47   ` [PATCH v4 00/11] QRTR Multi-endpoint support Mihai Moldovan

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=20250730175712.76c3e2a7@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=ionic@ionic.de \
    --cc=kuniyu@google.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.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).