From: Aaron Conole <aconole@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Pravin B Shelar <pshelar@ovn.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Adrian Moreno <amorenoz@redhat.com>,
Eelco Chaudron <echaudro@redhat.com>
Subject: Re: [PATCH net 4/4] selftests: openvswitch: Fix the ct_tuple for v4
Date: Wed, 11 Oct 2023 09:41:09 -0400 [thread overview]
Message-ID: <f7t5y3dcm4q.fsf@redhat.com> (raw)
In-Reply-To: <417e00407c64ccc39fce35bdb41b6765363d9fb1.camel@redhat.com> (Paolo Abeni's message of "Tue, 10 Oct 2023 12:31:05 +0200")
Paolo Abeni <pabeni@redhat.com> writes:
> On Fri, 2023-10-06 at 11:12 -0400, Aaron Conole wrote:
>> Caught during code review.
>
> Since there are a few other small things, please additionally expand
> this changelog briefly describing the addressed problem and it's
> consequences.
ACK. will fix in v2. Thanks Paolo!
> Thanks,
>
> Paolo
prev parent reply other threads:[~2023-10-11 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 15:12 [PATCH net 0/4] selftests: openvswitch: Minor fixes for some systems Aaron Conole
2023-10-06 15:12 ` [PATCH net 1/4] selftests: openvswitch: Add version check for pyroute2 Aaron Conole
2023-10-10 10:25 ` Paolo Abeni
2023-10-11 13:40 ` Aaron Conole
2023-10-06 15:12 ` [PATCH net 2/4] selftests: openvswitch: Catch cases where the tests are killed Aaron Conole
2023-10-06 15:12 ` [PATCH net 3/4] selftests: openvswitch: Skip drop testing on older kernels Aaron Conole
2023-10-10 10:29 ` Paolo Abeni
2023-10-11 13:40 ` Aaron Conole
2023-10-06 15:12 ` [PATCH net 4/4] selftests: openvswitch: Fix the ct_tuple for v4 Aaron Conole
2023-10-10 10:31 ` Paolo Abeni
2023-10-11 13:41 ` Aaron Conole [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=f7t5y3dcm4q.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.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).