public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Amir Vadai <amirv@mellanox.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org,
	Richard Cochran <richardcochran@gmail.com>,
	Or Gerlitz <ogerlitz@mellanox.com>,
	Eugenia Emantayev <eugenia@mellanox.com>
Subject: Re: [PATCH net-next V3 5/5] net/mlx4_en: Add a service task
Date: Thu, 25 Apr 2013 19:39:08 -0700	[thread overview]
Message-ID: <1366943948.8964.185.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAJZOPZLFtgVzk0YTzDkq1pGife6xTGH8tRtMYK=9nsTZFZmwQg@mail.gmail.com>

On Fri, 2013-04-26 at 05:24 +0300, Or Gerlitz wrote:

> Hi Eric,
> 
> This is fixed in "[PATCH V1 net-next 2/8] net/mlx4_en: Disable HW
> clock overflow check when no HW support"
> http://marc.info/?l=linux-netdev&m=136690338314540&w=2
> 

OK thanks, I missed it because the patch serie had the following label :

"[PATCH V1 net-next 0/8] net/mlx4: Add support to SRIOV VF management
ndo calls"

      reply	other threads:[~2013-04-26  2:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 16:06 [PATCH net-next V3 0/5] net/mlx4: HW timestamping support Amir Vadai
2013-04-23 16:06 ` [PATCH net-next V3 1/5] net/mlx4_core: Add timestamping device capability Amir Vadai
2013-04-23 16:06 ` [PATCH net-next V3 2/5] net/mlx4_core: Read HCA frequency and map internal clock Amir Vadai
2013-04-23 16:06 ` [PATCH net-next V3 3/5] net/mlx4_en: Add HW timestamping (TS) support Amir Vadai
2013-04-25 19:26   ` Richard Cochran
2013-04-28  6:33     ` Amir Vadai
2013-04-28  7:46       ` Richard Cochran
2013-04-28  8:00         ` Amir Vadai
2013-04-23 16:06 ` [PATCH net-next V3 4/5] net/mlx4_en: Support software timestamping Amir Vadai
2013-04-23 16:06 ` [PATCH net-next V3 5/5] net/mlx4_en: Add a service task Amir Vadai
2013-04-26  0:13   ` Eric Dumazet
2013-04-26  2:24     ` Or Gerlitz
2013-04-26  2:39       ` Eric Dumazet [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=1366943948.8964.185.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=amirv@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=eugenia@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=or.gerlitz@gmail.com \
    --cc=richardcochran@gmail.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