From: Simon Horman <horms@kernel.org>
To: Karol Kolacinski <karol.kolacinski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
richardcochran@gmail.com, Milena Olech <milena.olech@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 2/4] ice: refactor ice_sq_send_cmd and ice_shutdown_sq
Date: Fri, 6 Jun 2025 13:50:29 +0100 [thread overview]
Message-ID: <20250606125029.GC120308@horms.kernel.org> (raw)
In-Reply-To: <20250520110823.1937981-8-karol.kolacinski@intel.com>
On Tue, May 20, 2025 at 01:06:27PM +0200, Karol Kolacinski wrote:
> Refactor ice_sq_send_cmd() and ice_shutdown_sq() to be able to use
> a simpler locking, e.g. for new methods, which depend on the control
> queue.
>
> Reviewed-by: Milena Olech <milena.olech@intel.com>
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Karol Kolacinski <karol.kolacinski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
richardcochran@gmail.com, Milena Olech <milena.olech@intel.com>
Subject: Re: [PATCH iwl-next 2/4] ice: refactor ice_sq_send_cmd and ice_shutdown_sq
Date: Fri, 6 Jun 2025 13:50:29 +0100 [thread overview]
Message-ID: <20250606125029.GC120308@horms.kernel.org> (raw)
In-Reply-To: <20250520110823.1937981-8-karol.kolacinski@intel.com>
On Tue, May 20, 2025 at 01:06:27PM +0200, Karol Kolacinski wrote:
> Refactor ice_sq_send_cmd() and ice_shutdown_sq() to be able to use
> a simpler locking, e.g. for new methods, which depend on the control
> queue.
>
> Reviewed-by: Milena Olech <milena.olech@intel.com>
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-06-06 12:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 11:06 [Intel-wired-lan] [PATCH iwl-next 0/4] ice: Read Tx timestamps in the IRQ top half Karol Kolacinski
2025-05-20 11:06 ` Karol Kolacinski
2025-05-20 11:06 ` [Intel-wired-lan] [PATCH iwl-next 1/4] ice: skip completion for sideband queue writes Karol Kolacinski
2025-05-20 11:06 ` Karol Kolacinski
2025-05-22 6:47 ` [Intel-wired-lan] " Paul Menzel
2025-06-06 12:50 ` Simon Horman
2025-06-06 12:50 ` Simon Horman
2025-05-20 11:06 ` [Intel-wired-lan] [PATCH iwl-next 2/4] ice: refactor ice_sq_send_cmd and ice_shutdown_sq Karol Kolacinski
2025-05-20 11:06 ` Karol Kolacinski
2025-06-06 12:50 ` Simon Horman [this message]
2025-06-06 12:50 ` Simon Horman
2025-05-20 11:06 ` [Intel-wired-lan] [PATCH iwl-next 3/4] ice: use spin_lock for sideband queue send queue Karol Kolacinski
2025-05-20 11:06 ` Karol Kolacinski
2025-06-06 12:49 ` [Intel-wired-lan] " Simon Horman
2025-06-06 12:49 ` Simon Horman
2025-05-20 11:06 ` [Intel-wired-lan] [PATCH iwl-next 4/4] ice: read Tx timestamps in the IRQ top half Karol Kolacinski
2025-05-20 11:06 ` Karol Kolacinski
2025-06-06 12:50 ` [Intel-wired-lan] " Simon Horman
2025-06-06 12:50 ` Simon Horman
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=20250606125029.GC120308@horms.kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=karol.kolacinski@intel.com \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.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 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.