From: Simon Horman <simon.horman@corigine.com>
To: Aaron Conole <aconole@redhat.com>
Cc: dev@openvswitch.org, netdev@vger.kernel.org,
Ilya Maximets <i.maximets@ovn.org>,
Eric Dumazet <edumazet@google.com>,
linux-kselftest@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
shuah@kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [ovs-dev] [PATCH net-next 0/4] selftests: openvswitch: add flow programming cases
Date: Thu, 29 Jun 2023 17:03:34 +0200 [thread overview]
Message-ID: <ZJ2dRueF4SG3sG/O@corigine.com> (raw)
In-Reply-To: <f7tjzvmmp4w.fsf@redhat.com>
On Thu, Jun 29, 2023 at 08:25:35AM -0400, Aaron Conole wrote:
> Simon Horman <simon.horman@corigine.com> writes:
>
> > On Wed, Jun 28, 2023 at 12:27:10PM -0400, Aaron Conole wrote:
> >> The openvswitch selftests currently contain a few cases for managing the
> >> datapath, which includes creating datapath instances, adding interfaces,
> >> and doing some basic feature / upcall tests. This is useful to validate
> >> the control path.
> >>
> >> Add the ability to program some of the more common flows with actions. This
> >> can be improved overtime to include regression testing, etc.
> >
> > Hi Aaron,
> >
> > sorry but:
> >
> > [text from Jakub]
> >
> > ## Form letter - net-next-closed
> >
> > The merge window for v6.5 has begun and therefore net-next is closed
> > for new drivers, features, code refactoring and optimizations.
> > We are currently accepting bug fixes only.
> >
> > Please repost when net-next reopens after July 10th.
> >
> > RFC patches sent for review only are obviously welcome at any time.
> >
> > See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
> > --
> > pw-bot: defer
>
> Thanks Simon. I skipped looking at the ML this time and used the site
> setup for random German tourists:
> http://vger.kernel.org/~davem/net-next.html
>
> I guess I'll stop using it and just check the ML as normal :) Sorry for
> the noise.
Thanks Aaron,
unfortunately that page is not always up to date.
prev parent reply other threads:[~2023-06-29 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 16:27 [PATCH net-next 0/4] selftests: openvswitch: add flow programming cases Aaron Conole
2023-06-28 16:27 ` [PATCH net-next 1/4] selftests: openvswitch: add an initial flow programming case Aaron Conole
2023-07-07 15:40 ` [ovs-dev] " Adrian Moreno
2023-07-27 15:34 ` Aaron Conole
2023-06-28 16:27 ` [PATCH net-next 2/4] selftests: openvswitch: add a test for ipv4 forwarding Aaron Conole
2023-06-28 16:27 ` [PATCH net-next 3/4] selftests: openvswitch: add basic ct test case parsing Aaron Conole
2023-07-07 9:54 ` [ovs-dev] " Adrian Moreno
2023-07-10 16:21 ` Aaron Conole
2023-06-28 16:27 ` [PATCH net-next 4/4] selftests: openvswitch: add ct-nat test case with ipv4 Aaron Conole
2023-07-07 10:12 ` [ovs-dev] " Adrian Moreno
2023-07-10 16:25 ` Aaron Conole
2023-06-28 20:14 ` [ovs-dev] [PATCH net-next 0/4] selftests: openvswitch: add flow programming cases Simon Horman
2023-06-29 12:25 ` Aaron Conole
2023-06-29 15:03 ` Simon Horman [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=ZJ2dRueF4SG3sG/O@corigine.com \
--to=simon.horman@corigine.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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