From: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org, Roland Dreier <rdreier@cisco.com>,
general@lists.openfabrics.org
Subject: [ofa-general] Re: Re: [PATCH] mlx4_en: Pause parameters per port
Date: Thu, 06 Nov 2008 08:53:40 +0200 [thread overview]
Message-ID: <49129474.1030607@mellanox.co.il> (raw)
In-Reply-To: <49128472.7080607@pobox.com>
Jeff Garzik wrote:
> Is this a regression fix? It doesn't look like one to me, so I am
> planning to hold this for 2.6.29 (davem/net-next-2.6.git), unless there
> are problems with this plan?
>
This is regression fix. When setting pause parameters for one port, they would only change for that port,
but both of the ports report the same parameters. It means that the second port reports wrong pause parameters.
Yevgeny
prev parent reply other threads:[~2008-11-06 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 14:48 [ofa-general] [PATCH] mlx4_en: Pause parameters per port Yevgeny Petrilin
2008-11-05 17:58 ` Roland Dreier
2008-11-06 5:45 ` Jeff Garzik
2008-11-06 6:53 ` Yevgeny Petrilin [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=49129474.1030607@mellanox.co.il \
--to=yevgenyp@mellanox.co.il \
--cc=general@lists.openfabrics.org \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.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).