From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: donald.hunter@gmail.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
vadim.fedorenko@linux.dev, jiri@resnulli.us,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, aleksandr.loktionov@intel.com,
corbet@lwn.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-rdma@vger.kernel.org, linux-doc@vger.kernel.org,
Milena Olech <milena.olech@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v6 3/3] ice: add ref-sync dpll pins
Date: Mon, 16 Jun 2025 15:12:23 -0700 [thread overview]
Message-ID: <20250616151223.52254699@kernel.org> (raw)
In-Reply-To: <20250613200655.1712561-4-arkadiusz.kubalewski@intel.com>
On Fri, 13 Jun 2025 22:06:55 +0200 Arkadiusz Kubalewski wrote:
> - rebase and align with introducation of software pins
Another conflict, probably with the other DPLL series.
One more respin, please.
--
pw-bot: cr
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: donald.hunter@gmail.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
vadim.fedorenko@linux.dev, jiri@resnulli.us,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, aleksandr.loktionov@intel.com,
corbet@lwn.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-rdma@vger.kernel.org, linux-doc@vger.kernel.org,
Milena Olech <milena.olech@intel.com>
Subject: Re: [PATCH net-next v6 3/3] ice: add ref-sync dpll pins
Date: Mon, 16 Jun 2025 15:12:23 -0700 [thread overview]
Message-ID: <20250616151223.52254699@kernel.org> (raw)
In-Reply-To: <20250613200655.1712561-4-arkadiusz.kubalewski@intel.com>
On Fri, 13 Jun 2025 22:06:55 +0200 Arkadiusz Kubalewski wrote:
> - rebase and align with introducation of software pins
Another conflict, probably with the other DPLL series.
One more respin, please.
--
pw-bot: cr
next prev parent reply other threads:[~2025-06-16 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 20:06 [Intel-wired-lan] [PATCH net-next v6 0/3] dpll: add Reference SYNC feature Arkadiusz Kubalewski
2025-06-13 20:06 ` Arkadiusz Kubalewski
2025-06-13 20:06 ` [Intel-wired-lan] [PATCH net-next v6 1/3] dpll: add reference-sync netlink attribute Arkadiusz Kubalewski
2025-06-13 20:06 ` Arkadiusz Kubalewski
2025-06-13 20:06 ` [Intel-wired-lan] [PATCH net-next v6 2/3] dpll: add reference sync get/set Arkadiusz Kubalewski
2025-06-13 20:06 ` Arkadiusz Kubalewski
2025-06-13 20:06 ` [Intel-wired-lan] [PATCH net-next v6 3/3] ice: add ref-sync dpll pins Arkadiusz Kubalewski
2025-06-13 20:06 ` Arkadiusz Kubalewski
2025-06-16 22:12 ` Jakub Kicinski [this message]
2025-06-16 22:12 ` Jakub Kicinski
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=20250616151223.52254699@kernel.org \
--to=kuba@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--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=jiri@resnulli.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.