From: Jakub Kicinski <kuba@kernel.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"Aleksandr Loktionov" <aleksandr.loktionov@intel.com>,
Simon Horman <horms@kernel.org>, Jiri Pirko <jiri@resnulli.us>,
<netdev@vger.kernel.org>, Petr Oros <poros@redhat.com>,
Alexander Nowlin <alexander.nowlin@intel.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Subject: Re: [PATCH net 11/11] ice: add dpll peer notification for paired SMA and U.FL pins
Date: Wed, 29 Apr 2026 17:41:25 -0700 [thread overview]
Message-ID: <20260429174125.191f9e70@kernel.org> (raw)
In-Reply-To: <3c1f1894-e969-4dc2-914f-9e15db35dab5@intel.com>
On Wed, 29 Apr 2026 16:28:48 -0700 Jacob Keller wrote:
> Either way, to my eyes this looks like a pre-existing issue that may
> need some attention but I don't feel like it should block these fixes.
Yes, I think "fail to notify" is / should be handled by setting
an error on all listener sockets. It's very much not the job
for this series.
Looks like the series did not get ingested by Sashiko fully,
I kicked off another run locally, so probably won't get to
apply this today.
I don't have any "organic" comments :)
next prev parent reply other threads:[~2026-04-30 0:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 5:22 [PATCH net 00/11] Intel Wired LAN Update 2026-04-27 (ice, iavf) Jacob Keller
2026-04-28 5:22 ` [PATCH net 01/11] iavf: rename IAVF_VLAN_IS_NEW to IAVF_VLAN_ADDING Jacob Keller
2026-04-28 5:22 ` [PATCH net 02/11] iavf: stop removing VLAN filters from PF on interface down Jacob Keller
2026-04-28 5:22 ` [PATCH net 03/11] iavf: wait for PF confirmation before removing VLAN filters Jacob Keller
2026-04-28 5:22 ` [PATCH net 04/11] iavf: add VIRTCHNL_OP_ADD_VLAN to success completion handler Jacob Keller
2026-04-28 5:22 ` [PATCH net 05/11] ice: fix NULL pointer dereference in ice_reset_all_vfs() Jacob Keller
2026-04-28 5:22 ` [PATCH net 06/11] ice: fix infinite recursion in ice_cfg_tx_topo via ice_init_dev_hw Jacob Keller
2026-04-28 5:22 ` [PATCH net 07/11] ice: fix missing SMA pin initialization in DPLL subsystem Jacob Keller
2026-04-28 5:22 ` [PATCH net 08/11] ice: fix SMA and U.FL pin state changes affecting paired pin Jacob Keller
2026-04-28 5:22 ` [PATCH net 09/11] dpll: export __dpll_pin_change_ntf() for use under dpll_lock Jacob Keller
2026-04-28 5:22 ` [PATCH net 10/11] ice: fix missing dpll notifications for SW pins Jacob Keller
2026-04-28 5:22 ` [PATCH net 11/11] ice: add dpll peer notification for paired SMA and U.FL pins Jacob Keller
2026-04-29 23:28 ` Jacob Keller
2026-04-30 0:41 ` Jakub Kicinski [this message]
2026-04-30 9:36 ` Paolo Abeni
2026-04-30 10:00 ` [PATCH net 00/11] Intel Wired LAN Update 2026-04-27 (ice, iavf) patchwork-bot+netdevbpf
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=20260429174125.191f9e70@kernel.org \
--to=kuba@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=alexander.nowlin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@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