From: naamax.meir <naamax.meir@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v1 1/1] igc: Fix infinite loop in release_swfw_sync
Date: Tue, 15 Mar 2022 10:04:48 +0200 [thread overview]
Message-ID: <c9536ff5-72ac-5b78-6eb3-e6c5f415433a@linux.intel.com> (raw)
In-Reply-To: <20220301133210.1433609-1-sasha.neftin@intel.com>
On 3/1/2022 15:32, Sasha Neftin wrote:
> An infinite loop may occur if we fail to acquire the HW semaphore,
> which is needed for resource release.
> This will typically happen if the hardware is surprise-removed.
> At this stage there is nothing to do, except log an error and quit.
>
> Suggested-by: Dima Ruinskiy<dima.ruinskiy@intel.com>
> Signed-off-by: Sasha Neftin<sasha.neftin@intel.com>
> ---
> drivers/net/ethernet/intel/igc/igc_i225.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
Tested-by: Naama Meir <naamax.meir@linux.intel.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20220315/e4f90db1/attachment.html>
prev parent reply other threads:[~2022-03-15 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 13:32 [Intel-wired-lan] [PATCH v1 1/1] igc: Fix infinite loop in release_swfw_sync Sasha Neftin
2022-03-15 8:04 ` naamax.meir [this message]
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=c9536ff5-72ac-5b78-6eb3-e6c5f415433a@linux.intel.com \
--to=naamax.meir@linux.intel.com \
--cc=intel-wired-lan@osuosl.org \
/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