From: David Miller <davem@davemloft.net>
To: vbridgers2013@gmail.com
Cc: netdev@vger.kernel.org, peppe.cavallaro@st.com, rayagond@vayavyalabs.com
Subject: Re: [PATCH net] Fix incorrect spinlock release in stmmac_ptp.c and incorrect PTP capabilities detection in PTP initialization.
Date: Sun, 29 Dec 2013 22:38:52 -0500 (EST) [thread overview]
Message-ID: <20131229.223852.1418279531462143872.davem@davemloft.net> (raw)
In-Reply-To: <1387559974-31872-1-git-send-email-vbridgers2013@gmail.com>
From: Vince Bridgers <vbridgers2013@gmail.com>
Date: Fri, 20 Dec 2013 11:19:34 -0600
> This patch corrects a problem in stmmac_ptp.c, functions
> stmmac_adjust_time and stmmac_adjust_freq where the incorrect spinlocks
> were released. This patch also addresses a problem in stmmac_main,
> function stmmac_init_ptp where the capability detection for
> advanced timestamping was masked by message masking.
>
> This patch was touch tested using linuxptp, and runs without the previously
> observed instabilities. More extensive testing is ongoing.
>
> Signed-off-by: Vince Bridgers <vbridgers2013@gmail.com>
Applied, but please provide a more suitable subject line next time.
Subject lines should, after "[PATCH net]" should have an appropriate
prefix followed by a colon and a space.
Here, that would be "stmmac: "
Also, your Subject line is exceedingly long, try to keep it down to
80 columns. I edited it to be:
stmmac: Fix incorrect spinlock release and PTP cap detection.
next prev parent reply other threads:[~2013-12-30 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 17:19 [PATCH net] Fix incorrect spinlock release in stmmac_ptp.c and incorrect PTP capabilities detection in PTP initialization Vince Bridgers
2013-12-30 3:38 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-20 14:49 Vince Bridgers
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=20131229.223852.1418279531462143872.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=rayagond@vayavyalabs.com \
--cc=vbridgers2013@gmail.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).