From: Richard Cochran <richardcochran@gmail.com>
To: Yangbo Lu <yangbo.lu@nxp.com>
Cc: Fabio Estevam <festevam@gmail.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v2] net: gianfar_ptp: move set_fipers() to spinlock protecting area
Date: Mon, 8 Jan 2018 19:39:37 -0800 [thread overview]
Message-ID: <20180109033937.fnppxraqb7ylikdg@localhost> (raw)
In-Reply-To: <20180109030233.16013-1-yangbo.lu@nxp.com>
On Tue, Jan 09, 2018 at 11:02:33AM +0800, Yangbo Lu wrote:
> set_fipers() calling should be protected by spinlock in
> case that any interrupt breaks related registers setting
> and the function we expect. This patch is to move set_fipers()
> to spinlock protecting area in ptp_gianfar_adjtime().
>
> Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
Acked-by: Richard Cochran <richardcochran@gmail.com>
next prev parent reply other threads:[~2018-01-09 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 3:02 [v2] net: gianfar_ptp: move set_fipers() to spinlock protecting area Yangbo Lu
2018-01-09 3:39 ` Richard Cochran [this message]
2018-01-09 9:15 ` Fabio Estevam
2018-01-10 19:54 ` 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=20180109033937.fnppxraqb7ylikdg@localhost \
--to=richardcochran@gmail.com \
--cc=claudiu.manoil@nxp.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.