From: Richard Cochran <richardcochran@gmail.com>
To: Shawn Bohrer <shawn.bohrer@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Or Gerlitz <ogerlitz@mellanox.com>,
Amir Vadai <amirv@mellanox.com>,
netdev@vger.kernel.org, tomk@rgmadvisors.com,
Hadar Hen Zion <hadarh@mellanox.com>,
Shawn Bohrer <sbohrer@rgmadvisors.com>
Subject: Re: [PATCH net-next v4 2/2] mlx4_en: Only cycle port if HW timestamp config changes
Date: Wed, 1 Jan 2014 10:47:28 +0100 [thread overview]
Message-ID: <20140101094728.GB7682@netboy> (raw)
In-Reply-To: <1388511580-3657-3-git-send-email-shawn.bohrer@gmail.com>
On Tue, Dec 31, 2013 at 11:39:40AM -0600, Shawn Bohrer wrote:
> From: Shawn Bohrer <sbohrer@rgmadvisors.com>
>
> If the hwtstamp_config matches what is currently set for the device then
> simply return. Without this change any program that tries to enable
> hardware timestamps will cause the link to cycle even if hardware
> timstamps were already enabled.
>
> Signed-off-by: Shawn Bohrer <sbohrer@rgmadvisors.com>
> ---
> drivers/net/ethernet/mellanox/mlx4/en_clock.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
Acked-by: Richard Cochran <richardcochran@gmail.com>
next prev parent reply other threads:[~2014-01-01 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 17:39 [PATCH net-next v4 0/2] mlx4_en: Add PTP support Shawn Bohrer
2013-12-31 17:39 ` [PATCH net-next v4 1/2] mlx4_en: Add PTP hardware clock Shawn Bohrer
2014-01-01 8:50 ` Hadar Hen-Zion
2014-01-02 3:06 ` David Miller
2014-01-01 9:46 ` [PATCH net-next v4 1/2] " Richard Cochran
2013-12-31 17:39 ` [PATCH net-next v4 2/2] mlx4_en: Only cycle port if HW timestamp config changes Shawn Bohrer
2014-01-01 8:52 ` Hadar Hen-Zion
2014-01-01 9:47 ` Richard Cochran [this message]
2014-01-02 8:32 ` [PATCH net-next v4 0/2] mlx4_en: Add PTP support 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=20140101094728.GB7682@netboy \
--to=richardcochran@gmail.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=hadarh@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=sbohrer@rgmadvisors.com \
--cc=shawn.bohrer@gmail.com \
--cc=tomk@rgmadvisors.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