From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v4 1/5] igb: introduce ptp_flags variable and use it to replace IGB_FLAG_PTP
Date: Wed, 25 May 2016 20:08:55 +0000 [thread overview]
Message-ID: <1464206935.31989.5.camel@intel.com> (raw)
In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B81F005BD@ORSMSX101.amr.corp.intel.com>
On Tue, 2016-05-24 at 23:37 +0000, Brown, Aaron F wrote:
> >
> > From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.
> > org] On
> > Behalf Of Jacob Keller
> > Sent: Tuesday, May 24, 2016 1:56 PM
> > To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
> > Subject: [Intel-wired-lan] [PATCH v4 1/5] igb: introduce ptp_flags
> > variable
> > and use it to replace IGB_FLAG_PTP
> >
> > Upcoming patches will introduce new PTP specific flags. To avoid
> > cluttering the normal flags variable, introduce PTP specific
> > "ptp_flags"
> > variable for this purpose, and move IGB_FLAG_PTP to become
> > IGB_PTP_ENABLED.
> >
> > Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> > ---
> > ?drivers/net/ethernet/intel/igb/igb.h?????| 5 ++++-
> > ?drivers/net/ethernet/intel/igb/igb_ptp.c | 7 ++++---
> > ?2 files changed, 8 insertions(+), 4 deletions(-)
> >
> On a quick check this (v3) series resolves both the issues I
> described earlier.??All the systems I saw problem on are now happily
> bouncing ptp4l packets across the wire for more than a minute or
> two.??Given it would blow up almost immediately before those issues
> seem to be gone.??Now to put it through the rest of its paces ;)
Thanks.
Regards,
Jake
next prev parent reply other threads:[~2016-05-25 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 20:56 [Intel-wired-lan] [PATCH v4 1/5] igb: introduce ptp_flags variable and use it to replace IGB_FLAG_PTP Jacob Keller
2016-05-24 20:56 ` [Intel-wired-lan] [PATCH v4 2/5] igb: introduce IGB_PTP_OVERFLOW_CHECK flag Jacob Keller
2016-05-27 22:24 ` Brown, Aaron F
2016-05-24 20:56 ` [Intel-wired-lan] [PATCH v4 3/5] igb: re-use igb_ptp_reset in igb_ptp_init Jacob Keller
2016-05-27 22:24 ` Brown, Aaron F
2016-05-24 20:56 ` [Intel-wired-lan] [PATCH v4 4/5] igb: implement igb_ptp_suspend Jacob Keller
2016-05-27 22:24 ` Brown, Aaron F
2016-05-24 20:56 ` [Intel-wired-lan] [PATCH v4 5/5] igb: call igb_ptp_suspend during suspend/resume cycle Jacob Keller
2016-05-27 22:25 ` Brown, Aaron F
2016-05-24 20:57 ` [Intel-wired-lan] [PATCH v4 1/5] igb: introduce ptp_flags variable and use it to replace IGB_FLAG_PTP Keller, Jacob E
2016-05-24 23:37 ` Brown, Aaron F
2016-05-25 20:08 ` Keller, Jacob E [this message]
2016-05-27 22:23 ` Brown, Aaron F
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=1464206935.31989.5.camel@intel.com \
--to=jacob.e.keller@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.