From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Jiawen Wu <jiawenwu@trustnetic.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
horms@kernel.org, jacob.e.keller@intel.com,
netdev@vger.kernel.org, mengyuanlou@net-swift.com
Subject: Re: [PATCH net-next v5 1/4] net: wangxun: Add support for PTP clock
Date: Fri, 17 Jan 2025 16:03:35 +0000 [thread overview]
Message-ID: <df736add-784b-40c8-9982-ed8821a8bcb6@linux.dev> (raw)
In-Reply-To: <Z4p8ZuQaUe86Em9_@hoboy.vegasvil.org>
On 17/01/2025 15:51, Richard Cochran wrote:
> On Fri, Jan 17, 2025 at 02:15:01PM +0000, Vadim Fedorenko wrote:
>
>> there is no way ptp_clock_register() will return NULL,
>
> Really?
>
> include/linux/ptp_clock_kernel.h:
>
> 400 static inline struct ptp_clock *ptp_clock_register(struct ptp_clock_info *info,
> 401 struct device *parent)
> 402 { return NULL; }
>
> Also, sometimes the kernelDoc comments are correct, like in this case:
>
> 304 /**
> 305 * ptp_clock_register() - register a PTP hardware clock driver
> 306 *
> 307 * @info: Structure describing the new clock.
> 308 * @parent: Pointer to the parent device of the new clock.
> 309 *
> 310 * Returns a valid pointer on success or PTR_ERR on failure. If PHC
> 311 * support is missing at the configuration level, this function
> 312 * returns NULL, and drivers are expected to gracefully handle that
> 313 * case separately.
> 314 */
>
>
> Thanks,
> Richard
Well, yes, this case is a special one. Then maybe it's better to adjust
Kconfig and Makefile to avoid it?
next prev parent reply other threads:[~2025-01-17 16:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 6:20 [PATCH net-next v5 0/4] Support PTP clock for Wangxun NICs Jiawen Wu
2025-01-17 6:20 ` [PATCH net-next v5 1/4] net: wangxun: Add support for PTP clock Jiawen Wu
2025-01-17 14:15 ` Vadim Fedorenko
2025-01-17 15:51 ` Richard Cochran
2025-01-17 16:03 ` Vadim Fedorenko [this message]
2025-01-17 22:39 ` Jacob Keller
2025-01-19 1:42 ` Richard Cochran
2025-01-20 11:14 ` kernel test robot
2025-01-20 12:27 ` Vadim Fedorenko
2025-01-17 6:20 ` [PATCH net-next v5 2/4] net: wangxun: Support to get ts info Jiawen Wu
2025-01-17 6:20 ` [PATCH net-next v5 3/4] net: wangxun: Implement do_aux_work of ptp_clock_info Jiawen Wu
2025-01-17 6:20 ` [PATCH net-next v5 4/4] net: ngbe: Add support for 1PPS and TOD Jiawen Wu
2025-01-19 19:15 ` Richard Cochran
2025-01-19 19:16 ` [PATCH net-next v5 0/4] Support PTP clock for Wangxun NICs Richard Cochran
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=df736add-784b-40c8-9982-ed8821a8bcb6@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@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.