From: Alexander H Duyck <alexander.duyck@gmail.com>
To: Michal Schmidt <mschmidt@redhat.com>, intel-wired-lan@lists.osuosl.org
Cc: Ivan Vecera <ivecera@redhat.com>,
netdev@vger.kernel.org,
Patryk Piotrowski <patryk.piotrowski@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net v2 0/2] iavf: fix temporary deadlock and failure to set MAC address
Date: Fri, 16 Dec 2022 08:29:28 -0800 [thread overview]
Message-ID: <c4109e30b644df218b7e601071a64197bf17b1f4.camel@gmail.com> (raw)
In-Reply-To: <20221215225049.508812-1-mschmidt@redhat.com>
On Thu, 2022-12-15 at 23:50 +0100, Michal Schmidt wrote:
> This fixes an issue where setting the MAC address on iavf runs into a
> timeout and fails with EAGAIN.
>
> Changes in v2:
> - Removed unused 'ret' variable in patch 1.
> - Added patch 2 to fix another cause of the same timeout.
>
> Michal Schmidt (2):
> iavf: fix temporary deadlock and failure to set MAC address
> iavf: avoid taking rtnl_lock in adminq_task
>
> drivers/net/ethernet/intel/iavf/iavf.h | 4 +-
> .../net/ethernet/intel/iavf/iavf_ethtool.c | 10 +-
> drivers/net/ethernet/intel/iavf/iavf_main.c | 135 ++++++++++--------
> .../net/ethernet/intel/iavf/iavf_virtchnl.c | 8 +-
> 4 files changed, 86 insertions(+), 71 deletions(-)
>
The series looks good to me.
Reviewed-by: Alexander Duyck <alexanderduyck@fb.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2022-12-16 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 22:50 [Intel-wired-lan] [PATCH net v2 0/2] iavf: fix temporary deadlock and failure to set MAC address Michal Schmidt
2022-12-15 22:50 ` [Intel-wired-lan] [PATCH net 1/2] " Michal Schmidt
2023-01-19 12:10 ` Romanowski, Rafal
2022-12-15 22:50 ` [Intel-wired-lan] [PATCH net 2/2] iavf: avoid taking rtnl_lock in adminq_task Michal Schmidt
2022-12-16 16:29 ` Alexander H Duyck [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=c4109e30b644df218b7e601071a64197bf17b1f4.camel@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=patryk.piotrowski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox