From: Or Gerlitz <gerlitz.or@gmail.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
Yevgeny Petrilin <yevgenyp@mellanox.com>,
Eli Cohen <eli@mellanox.com>
Subject: Re: [PATCH net-next 0/8] Mellanox mlx5 driver update
Date: Tue, 29 Sep 2015 01:20:07 +0300 [thread overview]
Message-ID: <CAJ3xEMjWeQhUANyiBw3MjgpvnimEOsEmY66Kudu4LfOhZfpfcw@mail.gmail.com> (raw)
In-Reply-To: <1443167356-32095-1-git-send-email-ogerlitz@mellanox.com>
On Fri, Sep 25, 2015 at 10:49 AM, Or Gerlitz <ogerlitz@mellanox.com> wrote:
> Hi Dave,
>
> Bunch of changes from the team, while warming engines for the
> upcoming SRIOV support.
Hi Dave,
FWIW - I will be OOO for the rest of this week, so in case you'll have
some comments/questions on the series will see them only next week.
Or.
next prev parent reply other threads:[~2015-09-28 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 7:49 [PATCH net-next 0/8] Mellanox mlx5 driver update Or Gerlitz
2015-09-25 7:49 ` [PATCH net-next 1/8] net/mlx5e: Priv state flag not rolled-back upon netdev open error Or Gerlitz
2015-09-25 7:49 ` [PATCH net-next 2/8] net/mlx5_core: Fix struct type in the DESTROY_TIR/TIS device commands Or Gerlitz
2015-09-25 7:49 ` [PATCH net-next 3/8] net/mlx5_core: Remove redundant "err" variable usage Or Gerlitz
2015-09-25 7:49 ` [PATCH net-next 4/8] net/mlx5_core: Fix async commands return code Or Gerlitz
2015-09-25 7:49 ` [PATCH net-next 5/8] net/mlx5_core: Fix notification of page supplement error Or Gerlitz
2015-09-25 7:49 ` [PATCH net-next 6/8] net/mlx5_core: New init and exit flow for mlx5_core Or Gerlitz
2015-09-25 7:49 ` [PATCH net-next 7/8] net/mlx5_core: Fix wrong name in struct Or Gerlitz
2015-09-25 7:49 ` [PATCH net-next 8/8] net/mlx5_core: Update health syndromes Or Gerlitz
2015-09-28 22:20 ` Or Gerlitz [this message]
2015-09-29 5:20 ` [PATCH net-next 0/8] Mellanox mlx5 driver update David Miller
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=CAJ3xEMjWeQhUANyiBw3MjgpvnimEOsEmY66Kudu4LfOhZfpfcw@mail.gmail.com \
--to=gerlitz.or@gmail.com \
--cc=davem@davemloft.net \
--cc=eli@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).