From: Jakub Kicinski <kuba@kernel.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: davem@davemloft.net, bjorn.andersson@linaro.org,
manivannan.sadhasivam@linaro.org, cjhuang@codeaurora.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/5] net: qrtr: Add distant node support
Date: Sat, 7 Nov 2020 16:26:40 -0800 [thread overview]
Message-ID: <20201107162640.357a2b6f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <1604684010-24090-1-git-send-email-loic.poulain@linaro.org>
On Fri, 6 Nov 2020 18:33:25 +0100 Loic Poulain wrote:
> QRTR protocol allows a node to communicate with an other non-immediate
> node via an intermdediate immediate node acting as a 'bridge':
>
> node-0 <=> node-1 <=> node-2
>
> This is currently not supported in this upstream version and this
> series aim to fix that.
>
> This series is V2 because changes 1, 2 and 3 have already been submitted
> separately on LKML.
Looks like patch 1 is a bug fix and patches 2-5 add a new feature.
Is that correct?
If so first one needs to go to net and then onto 5.10, and the rest
to net-next for 5.11.
next prev parent reply other threads:[~2020-11-08 0:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 17:33 [PATCH v2 0/5] net: qrtr: Add distant node support Loic Poulain
2020-11-06 17:33 ` [PATCH v2 1/5] net: qrtr: Fix port ID for control messages Loic Poulain
2020-11-06 17:33 ` [PATCH v2 2/5] net: qrtr: Allow forwarded services Loic Poulain
2020-11-06 17:33 ` [PATCH v2 3/5] net: qrtr: Allow non-immediate node routing Loic Poulain
2020-11-06 17:33 ` [PATCH v2 4/5] net: qrtr: Add GFP flags parameter to qrtr_alloc_ctrl_packet Loic Poulain
2020-11-06 17:33 ` [PATCH v2 5/5] net: qrtr: Release distant nodes along the bridge node Loic Poulain
2020-11-08 0:26 ` Jakub Kicinski [this message]
2020-11-09 8:49 ` [PATCH v2 0/5] net: qrtr: Add distant node support Loic Poulain
2020-11-09 18:39 ` Jakub Kicinski
2020-11-10 9:03 ` Loic Poulain
2020-11-10 17:44 ` Jakub Kicinski
2020-11-11 23:31 ` Jakub Kicinski
2020-11-12 3:14 ` Manivannan Sadhasivam
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=20201107162640.357a2b6f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=cjhuang@codeaurora.org \
--cc=davem@davemloft.net \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.org \
/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).