All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose Abreu <Jose.Abreu@synopsys.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jose Abreu <Jose.Abreu@synopsys.com>,
	"David S. Miller" <davem@davemloft.net>,
	Joao Pinto <Joao.Pinto@synopsys.com>,
	Giuseppe Cavallaro <peppe.cavallaro@st.com>,
	Alexandre Torgue <alexandre.torgue@st.com>
Subject: [PATCH net-next 0/3] net: stmmac: Fix HW timestamping
Date: Fri, 20 Oct 2017 14:37:33 +0100	[thread overview]
Message-ID: <cover.1508506265.git.joabreu@synopsys.com> (raw)

Hi,

Three fixes for HW timestamping feature, all of them for RX side.

Best regards,
Jose Miguel Abreu

David,

I'm targeting this for -next but teel free to apply this in
your -fixes tree if you think its needed. Though, I don't
think anyone is using HW timestamping because these bugs would
appear immediatly.

Cc: David S. Miller <davem@davemloft.net>
Cc: Joao Pinto <jpinto@synopsys.com>
Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>

Jose Abreu (3):
  net: stmmac: Add missing call to dev_kfree_skb()
  net: stmmac: Fix stmmac_get_rx_hwtstamp()
  net: stmmac: Prevent infinite loop in get_rx_timestamp_status()

 drivers/net/ethernet/stmicro/stmmac/dwmac4_descs.c |  2 +-
 drivers/net/ethernet/stmicro/stmmac/stmmac_main.c  | 14 +++++++-------
 2 files changed, 8 insertions(+), 8 deletions(-)

-- 
1.9.1

             reply	other threads:[~2017-10-20 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 13:37 Jose Abreu [this message]
2017-10-20 13:37 ` [PATCH net-next 1/3] net: stmmac: Add missing call to dev_kfree_skb() Jose Abreu
2017-10-20 13:37 ` [PATCH net-next 2/3] net: stmmac: Fix stmmac_get_rx_hwtstamp() Jose Abreu
2017-10-20 13:37 ` [PATCH net-next 3/3] net: stmmac: Prevent infinite loop in get_rx_timestamp_status() Jose Abreu
2017-10-22  2:06 ` [PATCH net-next 0/3] net: stmmac: Fix HW timestamping 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=cover.1508506265.git.joabreu@synopsys.com \
    --to=jose.abreu@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=alexandre.torgue@st.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.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 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.