From: David Miller <davem@davemloft.net>
To: or.gerlitz@gmail.com
Cc: ddutile@redhat.com, amirv@mellanox.com, ogerlitz@mellanox.com,
yevgenyp@mellanox.com, Narendra_K@dell.com,
Sreekanth_Reddy@dell.com, netdev@vger.kernel.org,
andy@greyhouse.net
Subject: Re: [PATCH net 2/2] net/mlx4_core: mlx4_init_slave() shouldn't access comm channel before PF is ready
Date: Thu, 06 Mar 2014 17:09:27 -0500 (EST) [thread overview]
Message-ID: <20140306.170927.196605336074788079.davem@davemloft.net> (raw)
In-Reply-To: <CAJZOPZKfZ3Lp7XwasR19M1QC+5+ksQst8SORAxi2A7NVeHp7qg@mail.gmail.com>
From: Or Gerlitz <or.gerlitz@gmail.com>
Date: Thu, 6 Mar 2014 23:58:19 +0200
> So... we were thinking that there is a mechanism that causes them to
> retry that init as long as they return -EPROBE_DEFER or they succeed,
> isn't that the case?
Indeed. When the PF returns from it's probe, all VFs that deferred
will retry.
Both patches applied, thanks.
prev parent reply other threads:[~2014-03-06 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 16:28 [PATCH net 0/2] net/mlx4_core: SR-IOV related fixes Amir Vadai
2014-03-06 16:28 ` [PATCH net 1/2] net/mlx4_core: Fix memory access error in mlx4_QUERY_DEV_CAP_wrapper() Amir Vadai
2014-03-06 16:28 ` [PATCH net 2/2] net/mlx4_core: mlx4_init_slave() shouldn't access comm channel before PF is ready Amir Vadai
2014-03-06 20:12 ` David Miller
2014-03-06 20:19 ` Or Gerlitz
2014-03-06 20:48 ` David Miller
2014-03-06 21:08 ` Or Gerlitz
2014-03-06 21:12 ` David Miller
2014-03-06 21:58 ` Or Gerlitz
2014-03-06 22:09 ` David Miller [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=20140306.170927.196605336074788079.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Narendra_K@dell.com \
--cc=Sreekanth_Reddy@dell.com \
--cc=amirv@mellanox.com \
--cc=andy@greyhouse.net \
--cc=ddutile@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=or.gerlitz@gmail.com \
--cc=yevgenyp@mellanox.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;
as well as URLs for NNTP newsgroup(s).