From: Marcelo Ricardo Leitner <mleitner@redhat.com>
To: Yevgeny Petrilin <yevgenyp@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: Possible issue with Mellanox mlx4/port handling
Date: Mon, 03 Sep 2012 15:16:53 -0300 [thread overview]
Message-ID: <5044F415.4010605@redhat.com> (raw)
In-Reply-To: <953B660C027164448AE903364AC447D28720CFEB@MTLDAG01.mtl.com>
On 09/03/2012 02:51 PM, Yevgeny Petrilin wrote:
>> If you can share, what can we expect it to be like? Like the chunk I suggested
>> above or is there anything else needed? I could notice only 6 places calling
>> get_promisc_qp() that way and couldn't find any other issue like that.
>>
>
> The fix is pretty much the same style like what you suggested.
Awesome. Thanks!
Marcelo
next prev parent reply other threads:[~2012-09-03 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 17:32 Possible issue with Mellanox mlx4/port handling Yevgeny Petrilin
2012-09-03 17:45 ` Marcelo Ricardo Leitner
2012-09-03 17:51 ` Yevgeny Petrilin
2012-09-03 18:16 ` Marcelo Ricardo Leitner [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-31 12:25 Possible issue with Mellanox be2net/port handling Marcelo Ricardo Leitner
2012-08-31 12:26 ` Possible issue with Mellanox mlx4/port handling Marcelo Ricardo Leitner
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=5044F415.4010605@redhat.com \
--to=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.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).