From: David Miller <davem@davemloft.net>
To: yangbo.lu@nxp.com
Cc: netdev@vger.kernel.org, claudiu.manoil@freescale.com
Subject: Re: [PATCH] gianfar: fix the last transmit buffer descriptor
Date: Fri, 03 Jun 2016 19:32:41 -0400 (EDT) [thread overview]
Message-ID: <20160603.193241.762160469427537530.davem@davemloft.net> (raw)
In-Reply-To: <1464860188-47854-1-git-send-email-yangbo.lu@nxp.com>
From: Yangbo Lu <yangbo.lu@nxp.com>
Date: Thu, 2 Jun 2016 17:36:28 +0800
> When the transmit hardware timestamping is enabled, an additional
> TxBD would be added and would be set as the last TxBD with TXBD_LAST
> and TXBD_INTERRUPT. However this has been broken by a patch recently.
> This made the software couldn't get transmit hardware timestamps and
> resulted in call trace. So, this patch is to fix this issue.
>
> Fixes: 48963b4492e9 ("gianfar: Remove redundant ops for do_tstamp
> from xmit()")
> Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
Applied, thanks.
prev parent reply other threads:[~2016-06-03 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 9:36 [PATCH] gianfar: fix the last transmit buffer descriptor Yangbo Lu
2016-06-02 11:02 ` Claudiu Manoil
2016-06-03 23:32 ` David Miller [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=20160603.193241.762160469427537530.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=claudiu.manoil@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=yangbo.lu@nxp.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;
as well as URLs for NNTP newsgroup(s).