From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
To: Simon Horman <horms@kernel.org>
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: Sun, 3 Sep 2023 17:56:36 +0530 [thread overview]
Message-ID: <290c7e5e-ddbb-c754-240f-a3017fed3801@quicinc.com> (raw)
In-Reply-To: <20230901141905.GJ140739@kernel.org>
Hi Simon,
On 9/1/2023 7:49 PM, Simon Horman wrote:
> 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.
>
There is as such no existing feature broken without these 2 patches
today. Then they might qualify as preparatory patches for adding
some features.
> 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.
>
Sure, then in that case looks like it belongs to 'net-next' and will
post V2 once the net-next is opened again.
> 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
>
> ok.
> ## 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.
>
ok, sure.
Regards,
Sricharan
prev parent reply other threads:[~2023-09-03 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 10:20 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 ` [PATCH net-next 0/2] net: qrtr: Few qrtr fixes Simon Horman
2023-09-03 12:26 ` Sricharan Ramabadhran [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=290c7e5e-ddbb-c754-240f-a3017fed3801@quicinc.com \
--to=quic_srichara@quicinc.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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_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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®