[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140806191744.GB6611@netboy>
Date: Wed, 6 Aug 2014 21:17:44 +0200
From: Richard Cochran <richardcochran@...il.com>
To: "Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@...s.com>
Cc: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
Nick Krause <xerofoify@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] Fix e1000e with Intel 82572EI that has no hardware
timestamp support
On Wed, Aug 06, 2014 at 02:32:16PM +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().
Why all the ragged lines? Better to use an editor that knows how to
justify a paragraph, more like this:
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().
That not only looks nicer, but it is also more readable.
Thanks,
Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists