From: Simon Horman <horms@kernel.org>
To: Sricharan Ramabadhran <quic_srichara@quicinc.com>
Cc: mani@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, quic_viswanat@quicinc.com
Subject: Re: [PATCH net-next 0/2] net: qrtr: Few qrtr fixes
Date: Fri, 1 Sep 2023 16:19:05 +0200 [thread overview]
Message-ID: <20230901141905.GJ140739@kernel.org> (raw)
In-Reply-To: <1693563621-1920-1-git-send-email-quic_srichara@quicinc.com>
On Fri, Sep 01, 2023 at 03:50:19PM +0530, Sricharan Ramabadhran wrote:
> Patch #1 fixes a race condition between qrtr driver and ns opening and
> sending data to a control port.
>
> Patch #2 address the issue with legacy targets sending the SSR
> notifications using DEL_PROC control message.
Hi Sricharan,
if these are fixes then they should be targeted at 'net' rather than
'net-next', and consideration should be given to supplying Fixes tags.
If these are not fixes, then please don't describe them as such.
In this case targeting net-next is correct, but it is currently closed,
as per the form letter below.
In either case please consider:
* Arranging local variables for new Networking code in
reverse xmas tree order - longest line to shortest
* Avoiding introducing new Sparse warnings
## Form letter - net-next-closed
The merge window for v6.6 has begun 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 Sept 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
next prev parent reply other threads:[~2023-09-01 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 10:20 [PATCH net-next 0/2] net: qrtr: Few qrtr fixes Sricharan Ramabadhran
2023-09-01 10:20 ` [PATCH net-next 1/2] net: qrtr: Prevent stale ports from sending Sricharan Ramabadhran
2023-09-01 14:11 ` Bjorn Andersson
2023-09-03 12:22 ` Sricharan Ramabadhran
2023-09-01 10:20 ` [PATCH net-next 2/2] net: qrtr: Add support for processing DEL_PROC type control message Sricharan Ramabadhran
2023-09-01 14:19 ` Simon Horman [this message]
2023-09-03 12:26 ` [PATCH net-next 0/2] net: qrtr: Few qrtr fixes Sricharan Ramabadhran
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=20230901141905.GJ140739@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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=quic_srichara@quicinc.com \
--cc=quic_viswanat@quicinc.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.