From: "Riccardo Paolo Bestetti" <pbl@bestov.io>
To: "Carlos Llamas" <cmllamas@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
"Hideaki YOSHIFUJI" <yoshfuji@linux-ipv6.org>,
"David Ahern" <dsahern@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, "Miaohe Lin" <linmiaohe@huawei.com>,
"Maciej Żenczykowski" <maze@google.com>
Subject: Re: [PATCH v2] ipv4: ping: fix bind address validity check
Date: Fri, 17 Jun 2022 20:26:07 +0200 [thread overview]
Message-ID: <CKSMCVPQ37DW.1WE1OE0CGQUX0@enhorning> (raw)
In-Reply-To: <YqyuOfvR4mesRTfe@google.com>
On Fri Jun 17, 2022 at 6:39 PM CEST, Carlos Llamas wrote:
> Thanks Riccardo for adding the test cases. I would appreciate it if next
> time you add a co-developed tag or maybe a separate commit as opposed to
> overriding the original author. This is fine though.
For context, I had the whole patch ready since a few days ago. This
morning I woke up to the v1, so I decided to just apply my tests and
send it off as a v2.
I evidently forgot to add the Co-developed-by in the process, for which
I apologize. I wish that could be fixed, but the patch was almost
immediately applied to the tree. (I stand by the choice of having a
single commit for the fix, however.)
Riccardo P. Bestetti
prev parent reply other threads:[~2022-06-17 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:54 [PATCH v2] ipv4: ping: fix bind address validity check Riccardo Paolo Bestetti
2022-06-17 11:30 ` patchwork-bot+netdevbpf
2022-06-17 23:45 ` Maciej Żenczykowski
2022-06-20 10:11 ` Greg KH
2022-06-23 18:18 ` Maciej Żenczykowski
2022-06-25 14:26 ` Greg KH
2022-06-18 0:32 ` NEEDS FIXING - Was: " Riccardo Paolo Bestetti
2022-06-18 2:58 ` Jakub Kicinski
2022-06-18 7:36 ` Riccardo Paolo Bestetti
2022-06-19 16:44 ` Riccardo Paolo Bestetti
2022-06-17 16:39 ` Carlos Llamas
2022-06-17 18:26 ` Riccardo Paolo Bestetti [this message]
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=CKSMCVPQ37DW.1WE1OE0CGQUX0@enhorning \
--to=pbl@bestov.io \
--cc=cmllamas@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernel-team@android.com \
--cc=kuba@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.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