netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mfo@canonical.com
Cc: dsahern@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] rtnetlink: fix rtnl_fdb_dump() for shorter family headers
Date: Fri, 05 Oct 2018 14:59:09 -0700 (PDT)	[thread overview]
Message-ID: <20181005.145909.1821026580059542057.davem@davemloft.net> (raw)
In-Reply-To: <CAO9xwp2Hbzz+vyiovwTEK+Z85TGdE8OpLPYhgqqAzr9Y0bHmeQ@mail.gmail.com>

From: Mauricio Faria de Oliveira <mfo@canonical.com>
Date: Fri, 5 Oct 2018 18:46:47 -0300

> On Fri, Oct 5, 2018 at 6:24 PM David Ahern <dsahern@gmail.com> wrote:
>>
>> 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.
>> >
> 
> Thanks.
> 
>> there was a v2 for this problem. I reviewed it and been testing it as
>> part of the strict dump patches.
> 
> The v2 is the applied patch :- ) [1]
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366

Oh right, I did apply v2.

  reply	other threads:[~2018-10-06  4:59 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
2018-10-05 21:46               ` Mauricio Faria de Oliveira
2018-10-05 21:59                 ` David Miller [this message]
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=20181005.145909.1821026580059542057.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --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).