From: Leon Romanovsky <leon@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Ido Kalir <idok@nvidia.com>,
linux-netdev <netdev@vger.kernel.org>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH iproute2-rc] rdma: Fix statistics bind/unbing argument handling
Date: Tue, 16 Feb 2021 08:16:27 +0200 [thread overview]
Message-ID: <YCtjO1Q2OnCOlEcu@unreal> (raw)
In-Reply-To: <04d7cd07-c3eb-c39c-bce1-3e9d4d1e4a27@gmail.com>
On Mon, Feb 15, 2021 at 06:56:26PM -0700, David Ahern wrote:
> On 2/14/21 10:40 PM, Leon Romanovsky wrote:
> > On Sun, Feb 14, 2021 at 08:26:16PM -0700, David Ahern wrote:
> >> what does iproute2-rc mean?
> >
> > Patch target is iproute2.git:
> > https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/
>
> so you are asking them to be committed for the 5.11 release?
This is a Fix to an existing issue (not theoretical one), so I was under
impression that it should go to -rc repo and not to -next.
Personally, I don't care to which repo will this fix be applied as long
as it is applied to one of the two iproute2 official repos.
Do you have clear guidance when should I send patches to iproute2-rc/iproute2-next?
Thanks
next prev parent reply other threads:[~2021-02-16 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 8:33 [PATCH iproute2-rc] rdma: Fix statistics bind/unbing argument handling Leon Romanovsky
2021-02-15 3:26 ` David Ahern
2021-02-15 5:40 ` Leon Romanovsky
2021-02-16 1:56 ` David Ahern
2021-02-16 6:16 ` Leon Romanovsky [this message]
2021-02-16 15:48 ` David Ahern
2021-02-18 8:44 ` Leon Romanovsky
2021-02-22 19:18 ` Stephen Hemminger
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=YCtjO1Q2OnCOlEcu@unreal \
--to=leon@kernel.org \
--cc=dsahern@gmail.com \
--cc=idok@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 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.