From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: "Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@etas.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCHv2] Fix e1000e with Intel 82572EI that has no hardware timestamp support
Date: Wed, 06 Aug 2014 23:34:12 -0700 [thread overview]
Message-ID: <1407393252.2244.1.camel@jtkirshe-mobl> (raw)
In-Reply-To: <fae55865c8fb40f8b2f05b56b070433c@FE-MBX1012.de.bosch.com>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
On Thu, 2014-08-07 at 06:29 +0000, Koehrer Mathias (ETAS/ESW5) wrote:
> With the Intel 82527EI (driver: e1000e) there is an issue when running
> the ptpd2 program, that leads to a kernel oops. The reason is here
> that
> in e1000_xmit_frame() a work queue will be scheduled that has not been
> initialized in this case. The work queue "tx_hwstamp_work" will only
> be
> initialized if adapter->flags & FLAG_HAS_HW_TIMESTAMP set. This check
> is missing in e1000_xmit_frame().
>
> The following patch adds the missing check.
>
> Signed-off-by: Mathias Koehrer <mathias.koehrer@etas.com>
>
> ---
> drivers/net/ethernet/intel/e1000e/netdev.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Thanks Mathias, I have added your patch to my queue for Dave's net tree.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-07 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 6:29 [PATCHv2] Fix e1000e with Intel 82572EI that has no hardware timestamp support Koehrer Mathias (ETAS/ESW5)
2014-08-07 6:34 ` Jeff Kirsher [this message]
2014-08-07 6:39 ` Koehrer Mathias (ETAS/ESW5)
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=1407393252.2244.1.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.koehrer@etas.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sergei.shtylyov@cogentembedded.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