From: Roland Dreier <rdreier@cisco.com>
To: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Cc: jgarzik@pobox.com, general@lists.openfabrics.org, netdev@vger.kernel.org
Subject: Re: [PATCH] mlx4_en: Pause parameters per port
Date: Wed, 05 Nov 2008 09:58:58 -0800 [thread overview]
Message-ID: <adamygerr4t.fsf@cisco.com> (raw)
In-Reply-To: <4911B244.30205@mellanox.co.il> (Yevgeny Petrilin's message of "Wed, 05 Nov 2008 16:48:36 +0200")
Jeff, please go ahead and merge both of these mlx4_en patches.
Yevgeny, I think it would be helpful for you to say (after the --- line,
so the git tools strip it automatically) whether I should merge the
patch or if it's something for Jeff, just to make things smoother and
clearer.
- R.
next prev parent reply other threads:[~2008-11-05 17:59 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 [this message]
2008-11-06 5:45 ` Jeff Garzik
2008-11-06 6:53 ` [ofa-general] Re: " Yevgeny Petrilin
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=adamygerr4t.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=general@lists.openfabrics.org \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.co.il \
/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).