From: David Miller <davem@davemloft.net>
To: alexg@mellanox.com
Cc: netdev@vger.kernel.org, yevgenyp@mellanox.com
Subject: Re: [PATCH 0/7] mlx4_en: bug fixes and performance enhancement
Date: Sun, 09 Oct 2011 23:44:41 -0400 (EDT) [thread overview]
Message-ID: <20111009.234441.799828124399111216.davem@davemloft.net> (raw)
In-Reply-To: <4E91BD1B.2040902@mellanox.com>
From: Alexander Guller <alexg@mellanox.com>
Date: Sun, 9 Oct 2011 17:26:19 +0200
> This is a series of patches for the mlx4_en driver generated against
> net-next tree. The patches include several bug fixes and a fix for
> a better initialization of TX interrupts.
Applied.
For some reason another copy of patch #3 was appended after the
end of patch #4. Make sure that doesn't happen next time.
prev parent reply other threads:[~2011-10-10 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 15:26 [PATCH 0/7] mlx4_en: bug fixes and performance enhancement Alexander Guller
2011-10-10 3:44 ` 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=20111009.234441.799828124399111216.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexg@mellanox.com \
--cc=netdev@vger.kernel.org \
--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).