From: Simon Horman <horms@kernel.org>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
przemyslaw.kitszel@intel.com, aleksandr.loktionov@intel.com,
jacob.e.keller@intel.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v6 0/4] Fix i40e/ice/iavf VF bonding after netdev lock changes
Date: Mon, 22 Jun 2026 11:31:59 +0100 [thread overview]
Message-ID: <20260622103159.GZ827683@horms.kernel.org> (raw)
In-Reply-To: <20260619061321.8554-1-jtornosm@redhat.com>
On Fri, Jun 19, 2026 at 08:13:15AM +0200, Jose Ignacio Tornos Martinez wrote:
> This series fixes VF bonding failures introduced by commit ad7c7b2172c3
> ("net: hold netdev instance lock during sysfs operations").
...
Hi Jose,
Unfortunately the Netdev CI was unable to apply this series cleanly against net.
Would you be able to rebase and repost?
--
pw-bot: changes-requested
next prev parent reply other threads:[~2026-06-22 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 6:13 [PATCH net v6 0/4] Fix i40e/ice/iavf VF bonding after netdev lock changes Jose Ignacio Tornos Martinez
2026-06-19 6:13 ` [PATCH net v6 1/4] iavf: return EBUSY if reset in progress or not ready during MAC change Jose Ignacio Tornos Martinez
2026-06-19 6:13 ` [PATCH net v6 2/4] i40e: skip unnecessary VF reset when setting trust Jose Ignacio Tornos Martinez
2026-06-19 6:13 ` [PATCH net v6 3/4] iavf: send MAC change request synchronously Jose Ignacio Tornos Martinez
2026-06-22 11:38 ` Przemek Kitszel
2026-06-19 6:13 ` [PATCH net v6 4/4] ice: skip unnecessary VF reset when setting trust Jose Ignacio Tornos Martinez
2026-06-22 11:18 ` Loktionov, Aleksandr
2026-06-22 11:19 ` Loktionov, Aleksandr
2026-06-22 10:31 ` Simon Horman [this message]
2026-06-22 10:51 ` [Intel-wired-lan] [PATCH net v6 0/4] Fix i40e/ice/iavf VF bonding after netdev lock changes Jose Ignacio Tornos Martinez
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=20260622103159.GZ827683@horms.kernel.org \
--to=horms@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
/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