From: Jakub Kicinski <kuba@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: Ahmed Zaki <ahmed.zaki@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
Emil Tantilov <emil.s.tantilov@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v1 0/4] fix locking issue
Date: Mon, 27 Jan 2025 09:42:47 -0800 [thread overview]
Message-ID: <20250127094247.40b169a1@kernel.org> (raw)
In-Reply-To: <95288bb1-8931-4d18-b8f6-25a4f6148afe@intel.com>
On Mon, 27 Jan 2025 09:11:41 +0100 Przemek Kitszel wrote:
> @netdev
> I would like to consider adding "in reset" state for the netdev,
> to prevent such behavior in more civilized way though.
Can you provide more context? We already have netif_device_detach()
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: "Singh, Krishneil K" <krishneil.k.singh@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Emil Tantilov" <emil.s.tantilov@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Ahmed Zaki <ahmed.zaki@intel.com>
Subject: Re: [PATCH iwl-net v1 0/4] fix locking issue
Date: Mon, 27 Jan 2025 09:42:47 -0800 [thread overview]
Message-ID: <20250127094247.40b169a1@kernel.org> (raw)
In-Reply-To: <95288bb1-8931-4d18-b8f6-25a4f6148afe@intel.com>
On Mon, 27 Jan 2025 09:11:41 +0100 Przemek Kitszel wrote:
> @netdev
> I would like to consider adding "in reset" state for the netdev,
> to prevent such behavior in more civilized way though.
Can you provide more context? We already have netif_device_detach()
next prev parent reply other threads:[~2025-01-27 17:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 18:48 [Intel-wired-lan] [PATCH iwl-net v1 0/4] fix locking issue Tarun K Singh
2024-11-05 18:48 ` Tarun K Singh
2024-11-05 18:48 ` [Intel-wired-lan] [PATCH iwl-net v1 1/4] idpf: Change function argument Tarun K Singh
2024-11-05 18:48 ` Tarun K Singh
2025-01-14 6:53 ` [Intel-wired-lan] " Singh, Krishneil K
2025-01-14 6:53 ` Singh, Krishneil K
2024-11-05 18:48 ` [Intel-wired-lan] [PATCH iwl-net v1 2/4] idpf: rename vport_ctrl_lock Tarun K Singh
2024-11-05 18:48 ` Tarun K Singh
2025-01-14 6:52 ` [Intel-wired-lan] " Singh, Krishneil K
2025-01-14 6:52 ` Singh, Krishneil K
2024-11-05 18:48 ` [Intel-wired-lan] [PATCH iwl-net v1 3/4] idpf: Add init, reinit, and deinit control lock Tarun K Singh
2024-11-05 18:48 ` Tarun K Singh
2025-01-14 6:50 ` [Intel-wired-lan] " Singh, Krishneil K
2025-01-14 6:50 ` Singh, Krishneil K
2024-11-05 18:48 ` [Intel-wired-lan] [PATCH iwl-net v1 4/4] idpf: add lock class key Tarun K Singh
2024-11-05 18:48 ` Tarun K Singh
2025-01-14 6:50 ` [Intel-wired-lan] " Singh, Krishneil K
2025-01-14 6:50 ` Singh, Krishneil K
2025-01-27 6:06 ` [Intel-wired-lan] [PATCH iwl-net v1 0/4] fix locking issue Singh, Krishneil K
2025-01-27 6:06 ` Singh, Krishneil K
2025-01-27 8:11 ` [Intel-wired-lan] " Przemek Kitszel
2025-01-27 8:11 ` Przemek Kitszel
2025-01-27 17:42 ` Jakub Kicinski [this message]
2025-01-27 17:42 ` Jakub Kicinski
2025-01-27 20:55 ` [Intel-wired-lan] " Przemek Kitszel
2025-01-27 20:55 ` Przemek Kitszel
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=20250127094247.40b169a1@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=emil.s.tantilov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--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 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.