From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: "Vecera, Ivan" <ivecera@redhat.com>,
"vadim.fedorenko@linux.dev" <vadim.fedorenko@linux.dev>,
"edumazet@google.com" <edumazet@google.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"donald.hunter@gmail.com" <donald.hunter@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>,
"Prathosh.Satish@microchip.com" <Prathosh.Satish@microchip.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"horms@kernel.org" <horms@kernel.org>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"jiri@resnulli.us" <jiri@resnulli.us>
Subject: Re: [Intel-wired-lan] [PATCH v14 net-next 03/13] dpll: fix stale iteration in dpll_pin_on_pin_unregister()
Date: Thu, 11 Jun 2026 10:41:09 -0700 [thread overview]
Message-ID: <20260611104109.34063873@kernel.org> (raw)
In-Reply-To: <20be8f49-4d85-430b-a651-c4aecd172a57@redhat.com>
On Thu, 11 Jun 2026 16:41:07 +0200 Paolo Abeni wrote:
> Fixes tag could be stripped when applying the patches as needed, and I
> think that could be preferable to a repost just for such thing, given
> the current PW load...
To be clear tho, this series has already been marked as changes
requested. Presumably based on the other comments?
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: "Nitka, Grzegorz" <grzegorz.nitka@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Oros, Petr" <poros@redhat.com>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Prathosh.Satish@microchip.com" <Prathosh.Satish@microchip.com>,
"Vecera, Ivan" <ivecera@redhat.com>,
"jiri@resnulli.us" <jiri@resnulli.us>,
"Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>,
"vadim.fedorenko@linux.dev" <vadim.fedorenko@linux.dev>,
"donald.hunter@gmail.com" <donald.hunter@gmail.com>,
"horms@kernel.org" <horms@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>
Subject: Re: [PATCH v14 net-next 03/13] dpll: fix stale iteration in dpll_pin_on_pin_unregister()
Date: Thu, 11 Jun 2026 10:41:09 -0700 [thread overview]
Message-ID: <20260611104109.34063873@kernel.org> (raw)
In-Reply-To: <20be8f49-4d85-430b-a651-c4aecd172a57@redhat.com>
On Thu, 11 Jun 2026 16:41:07 +0200 Paolo Abeni wrote:
> Fixes tag could be stripped when applying the patches as needed, and I
> think that could be preferable to a repost just for such thing, given
> the current PW load...
To be clear tho, this series has already been marked as changes
requested. Presumably based on the other comments?
next prev parent reply other threads:[~2026-06-11 17:41 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 18:30 [Intel-wired-lan] [PATCH v14 net-next 00/13] dpll/ice: Add generic DPLL type and full TX reference clock control for E825 Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 01/13] dpll: add generic DPLL type Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 02/13] dpll: allow registering FW-identified pin with a different DPLL Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 03/13] dpll: fix stale iteration in dpll_pin_on_pin_unregister() Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-08 16:51 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2026-06-08 16:51 ` Kubalewski, Arkadiusz
2026-06-09 6:50 ` Nitka, Grzegorz
2026-06-09 6:50 ` [Intel-wired-lan] " Nitka, Grzegorz
2026-06-11 8:50 ` Paolo Abeni
2026-06-11 8:50 ` [Intel-wired-lan] " Paolo Abeni
2026-06-11 10:01 ` Nitka, Grzegorz
2026-06-11 10:01 ` Nitka, Grzegorz
2026-06-11 14:41 ` [Intel-wired-lan] " Paolo Abeni
2026-06-11 14:41 ` Paolo Abeni
2026-06-11 17:41 ` Jakub Kicinski [this message]
2026-06-11 17:41 ` Jakub Kicinski
2026-06-11 18:36 ` Nitka, Grzegorz
2026-06-11 18:36 ` [Intel-wired-lan] " Nitka, Grzegorz
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 04/13] dpll: send delete notification before unregister in on-pin rollback Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-08 16:45 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2026-06-08 16:45 ` Kubalewski, Arkadiusz
2026-06-09 7:09 ` [Intel-wired-lan] " Nitka, Grzegorz
2026-06-09 7:09 ` Nitka, Grzegorz
2026-06-10 19:42 ` [Intel-wired-lan] " Nitka, Grzegorz
2026-06-10 19:42 ` Nitka, Grzegorz
2026-06-10 21:27 ` [Intel-wired-lan] " Nitka, Grzegorz
2026-06-10 21:27 ` Nitka, Grzegorz
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 05/13] dpll: emit per-dpll delete notifications in dpll_pin_on_pin_unregister() Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-08 16:40 ` Kubalewski, Arkadiusz
2026-06-08 16:40 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 06/13] dpll: guard sync-pair removal on full pin unregister Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-08 16:38 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2026-06-08 16:38 ` Kubalewski, Arkadiusz
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 07/13] dpll: balance create/delete notifications in __dpll_pin_(un)register Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-08 16:35 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2026-06-08 16:35 ` Kubalewski, Arkadiusz
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 08/13] dpll: extend pin notifier with notification source ID Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 09/13] dpll: allow fwnode pins to attempt state change without capability bit Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 10/13] ice: introduce TXC DPLL device and TX ref clock pin framework for E825 Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 11/13] ice: implement CPI support for E825C Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 12/13] ice: add Tx reference clock index handling to AN restart command Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
2026-06-07 18:30 ` [Intel-wired-lan] [PATCH v14 net-next 13/13] ice: implement E825 TX ref clock control and TXC hardware sync status Grzegorz Nitka
2026-06-07 18:30 ` Grzegorz Nitka
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=20260611104109.34063873@kernel.org \
--to=kuba@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.