From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Nick Desaulniers <ndesaulniers@google.com>,
David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kbuild test robot <lkp@intel.com>
Subject: Re: [PATCH net v2 1/2] ipv6: constify rt6_nexthop()
Date: Mon, 24 Jun 2019 20:18:37 +0200 [thread overview]
Message-ID: <3d7c16c4-9c3e-d18c-aad4-6583216ea457@6wind.com> (raw)
In-Reply-To: <CAKwvOdkqE_RVosXAe9ULePR8A37CHh6+JtDMaRAghUA41Y_+yg@mail.gmail.com>
Le 24/06/2019 à 19:37, Nick Desaulniers a écrit :
[snip]
>
> The author stated that this patch was no functional change. Nicolas,
> it can be helpful to include compiler warnings in the commit message
> when sending warning fixes, but it's not a big deal. Thanks for
> sending the patches.
>
Yep, but I was not aware of this compilation warning. As explained in the commit
log, the goal of this patch was to prepare the next one.
Regards,
Nicolas
next prev parent reply other threads:[~2019-06-24 18:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 12:34 [PATCH net] ipv6: fix neighbour resolution with raw socket Nicolas Dichtel
2019-06-20 15:12 ` David Ahern
2019-06-20 15:42 ` Nicolas Dichtel
2019-06-20 16:36 ` David Ahern
2019-06-20 16:47 ` David Ahern
2019-06-21 8:09 ` Nicolas Dichtel
2019-06-21 18:48 ` kbuild test robot
2019-06-23 0:07 ` David Miller
2019-06-23 0:08 ` David Miller
2019-06-24 14:01 ` [PATCH net v2 0/2] " Nicolas Dichtel
2019-06-24 14:01 ` [PATCH net v2 1/2] ipv6: constify rt6_nexthop() Nicolas Dichtel
2019-06-24 16:45 ` Nick Desaulniers
2019-06-24 17:06 ` David Miller
2019-06-24 17:17 ` Nick Desaulniers
2019-06-24 17:22 ` David Miller
2019-06-24 17:37 ` Nick Desaulniers
2019-06-24 18:18 ` Nicolas Dichtel [this message]
2019-06-24 20:27 ` David Miller
2019-06-24 14:01 ` [PATCH net v2 2/2] ipv6: fix neighbour resolution with raw socket Nicolas Dichtel
2019-06-26 20:26 ` [PATCH net v2 0/2] " David Miller
2019-10-14 9:34 ` Nicolas Dichtel
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=3d7c16c4-9c3e-d18c-aad4-6583216ea457@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.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).