From: Andrew Lunn <andrew@lunn.ch>
To: Antoine Tenart <antoine.tenart@bootlin.com>
Cc: davem@davemloft.net, richardcochran@gmail.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
netdev@vger.kernel.org, thomas.petazzoni@bootlin.com,
allan.nielsen@microchip.com
Subject: Re: [PATCH net-next v5 3/6] net: mscc: describe the PTP register range
Date: Sat, 10 Aug 2019 19:16:58 +0200 [thread overview]
Message-ID: <20190810171658.GG30120@lunn.ch> (raw)
In-Reply-To: <20190807092214.19936-4-antoine.tenart@bootlin.com>
On Wed, Aug 07, 2019 at 11:22:11AM +0200, Antoine Tenart wrote:
> This patch adds support for using the PTP register range, and adds a
> description of its registers. This bank is used when configuring PTP.
>
> Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2019-08-10 17:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 9:22 [PATCH net-next v5 0/6] net: mscc: PTP Hardware Clock (PHC) support Antoine Tenart
2019-08-07 9:22 ` [PATCH net-next v5 1/6] Documentation/bindings: net: ocelot: document the PTP bank Antoine Tenart
2019-08-10 17:14 ` Andrew Lunn
2019-08-07 9:22 ` [PATCH net-next v5 2/6] Documentation/bindings: net: ocelot: document the PTP ready IRQ Antoine Tenart
2019-08-10 17:15 ` Andrew Lunn
2019-08-07 9:22 ` [PATCH net-next v5 3/6] net: mscc: describe the PTP register range Antoine Tenart
2019-08-10 17:16 ` Andrew Lunn [this message]
2019-08-07 9:22 ` [PATCH net-next v5 4/6] net: mscc: improve the frame header parsing readability Antoine Tenart
2019-08-07 9:22 ` [PATCH net-next v5 5/6] net: mscc: remove the frame_info cpuq member Antoine Tenart
2019-08-10 17:18 ` Andrew Lunn
2019-08-07 9:22 ` [PATCH net-next v5 6/6] net: mscc: PTP Hardware Clock (PHC) support Antoine Tenart
2019-08-10 17:32 ` Andrew Lunn
2019-08-12 8:49 ` Antoine Tenart
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=20190810171658.GG30120@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=thomas.petazzoni@bootlin.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.