From: David Ahern <dsahern@gmail.com>
To: David Miller <davem@davemloft.net>, mfo@canonical.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] rtnetlink: fix rtnl_fdb_dump() for shorter family headers
Date: Fri, 5 Oct 2018 15:24:29 -0600 [thread overview]
Message-ID: <f64e7857-739d-0c06-6a3f-57db11ad1566@gmail.com> (raw)
In-Reply-To: <20181005.142230.532758670209479583.davem@davemloft.net>
On 10/5/18 3:22 PM, David Miller wrote:
> From: Mauricio Faria de Oliveira <mfo@canonical.com>
> Date: Mon, 1 Oct 2018 22:50:32 -0300
>
>> On Mon, Oct 1, 2018 at 12:38 PM Mauricio Faria de Oliveira
>> <mfo@canonical.com> wrote:
>>> Ok, thanks for your suggestions.
>>> I'll do some research/learning on them, and give it a try for a v2.
>>
>> FYI, that is "[PATCH v2 net-next] rtnetlink: fix rtnl_fdb_dump() for
>> ndmsg header".
>>
>> BTW, could please advise whether this should be net or net-next? It's a bug fix,
>> but it's late in the cycle, and this is not urgent (the problem has been around
>> since v4.12), so not sure it's really needed for v4.19.
>
> I've applied this to net and queued it up for -stable, thanks.
>
there was a v2 for this problem. I reviewed it and been testing it as
part of the strict dump patches.
next prev parent reply other threads:[~2018-10-06 4:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 19:35 [PATCH net-next] rtnetlink: fix rtnl_fdb_dump() for shorter family headers Mauricio Faria de Oliveira
2018-10-01 1:06 ` David Ahern
2018-10-01 12:44 ` Mauricio Faria de Oliveira
2018-10-01 15:01 ` David Ahern
2018-10-01 15:38 ` Mauricio Faria de Oliveira
2018-10-02 1:50 ` Mauricio Faria de Oliveira
2018-10-05 21:22 ` David Miller
2018-10-05 21:24 ` David Ahern [this message]
2018-10-05 21:46 ` Mauricio Faria de Oliveira
2018-10-05 21:59 ` David Miller
2018-10-05 21:58 ` David Miller
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=f64e7857-739d-0c06-6a3f-57db11ad1566@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=mfo@canonical.com \
--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).