From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: <sundeep.lkml@gmail.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>,
<richardcochran@gmail.com>, <netdev@vger.kernel.org>,
<sgoutham@marvell.com>, Aleksey Makarov <amakarov@marvell.com>,
Subbaraya Sundeep <sbhatta@marvell.com>
Subject: Re: [PATCH v6 net-next 3/3] octeontx2-pf: Add support for PTP clock
Date: Wed, 19 Aug 2020 10:00:36 -0700 [thread overview]
Message-ID: <20200819100036.00007b24@intel.com> (raw)
In-Reply-To: <1597770557-26617-4-git-send-email-sundeep.lkml@gmail.com>
sundeep.lkml@gmail.com wrote:
> From: Aleksey Makarov <amakarov@marvell.com>
>
> This patch adds PTP clock and uses it in Octeontx2
> network device. PTP clock uses mailbox calls to
> access the hardware counter on the RVU side.
>
> Co-developed-by: Subbaraya Sundeep <sbhatta@marvell.com>
> Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
> Signed-off-by: Aleksey Makarov <amakarov@marvell.com>
> Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
Besides that this driver doesn't have copyrights, I don't see many
problems with this part of the patch. I would like to see some of the
other patches have my comments addressed.
For this patch:
Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
next prev parent reply other threads:[~2020-08-19 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 17:09 [PATCH v6 net-next 0/3] Add PTP support for Octeontx2 sundeep.lkml
2020-08-18 17:09 ` [PATCH v6 net-next 1/3] octeontx2-af: Support to enable/disable HW timestamping sundeep.lkml
2020-08-19 15:38 ` Jesse Brandeburg
2020-08-20 13:25 ` sundeep subbaraya
2020-08-18 17:09 ` [PATCH v6 net-next 2/3] octeontx2-af: Add support for Marvell PTP coprocessor sundeep.lkml
2020-08-19 16:00 ` Jesse Brandeburg
2020-08-20 13:41 ` sundeep subbaraya
2020-08-18 17:09 ` [PATCH v6 net-next 3/3] octeontx2-pf: Add support for PTP clock sundeep.lkml
2020-08-19 17:00 ` Jesse Brandeburg [this message]
2020-08-20 13:42 ` sundeep subbaraya
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=20200819100036.00007b24@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=amakarov@marvell.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sundeep.lkml@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 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.