From: Aaron Conole <aconole@redhat.com>
To: Minxi Hou <houminxi@gmail.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
i.maximets@ovn.org, i.maximets@redhat.com
Subject: Re: [PATCH net-next 0/5] selftests: openvswitch: pylint cleanup for ovs-dpctl.py
Date: Wed, 13 May 2026 11:05:55 -0400 [thread overview]
Message-ID: <f7tlddnnycs.fsf@redhat.com> (raw)
In-Reply-To: <20260513124704.2610072-1-houminxi@gmail.com> (Minxi Hou's message of "Wed, 13 May 2026 20:47:04 +0800")
Minxi Hou <houminxi@gmail.com> writes:
> Hi Aaron,
Hi Minxi,
> This series depends on the v10 vlan/pop_vlan series (still in New state):
> https://patchwork.kernel.org/project/netdevbpf/list/?series=1093324
>
> Patchwork flagged apply failure because v10 isn't in the tree yet.
>
> Should I wait for v10 to land and resend, or is there a way to
> indicate the dependency so maintainers can apply them in order?
We should wait until all dependent series are merged; there isn't a way
to flog a series as depending on another as far as I'm aware.
I'll take a look at this series but please wait until the v10 is merged.
thanks!
> Thanks,
> Minxi
prev parent reply other threads:[~2026-05-13 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 12:12 [PATCH net-next 0/5] selftests: openvswitch: pylint cleanup for ovs-dpctl.py Minxi Hou
2026-05-13 12:12 ` [PATCH net-next 1/5] selftests: openvswitch: convert %-formatting to f-strings Minxi Hou
2026-05-13 12:12 ` [PATCH net-next 2/5] selftests: openvswitch: fix misc pylint warnings in ovs-dpctl.py Minxi Hou
2026-05-13 12:12 ` [PATCH net-next 3/5] selftests: openvswitch: rename classes and variables " Minxi Hou
2026-05-13 12:12 ` [PATCH net-next 4/5] selftests: openvswitch: add missing docstrings " Minxi Hou
2026-05-13 12:12 ` [PATCH net-next 5/5] selftests: openvswitch: suppress pylint complexity warnings Minxi Hou
2026-05-13 12:47 ` [PATCH net-next 0/5] selftests: openvswitch: pylint cleanup for ovs-dpctl.py Minxi Hou
2026-05-13 15:05 ` 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=f7tlddnnycs.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=dev@openvswitch.org \
--cc=houminxi@gmail.com \
--cc=i.maximets@ovn.org \
--cc=i.maximets@redhat.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