From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Shinu Chandran <s4superuser@gmail.com>, richardcochran@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ptp: ptp_clock: Fix coding style issues
Date: Sun, 26 Mar 2023 14:47:11 +0700 [thread overview]
Message-ID: <ZB/4f0H0y8COVR90@debian.me> (raw)
In-Reply-To: <20230325163135.2431367-1-s4superuser@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
On Sat, Mar 25, 2023 at 10:01:35PM +0530, Shinu Chandran wrote:
> diff --git a/drivers/ptp/ptp_clock.c b/drivers/ptp/ptp_clock.c
> index 62d4d29e7c05..8fe7f2ce9705 100644
> --- a/drivers/ptp/ptp_clock.c
> +++ b/drivers/ptp/ptp_clock.c
> @@ -129,6 +129,7 @@ static int ptp_clock_adjtime(struct posix_clock *pc, struct __kernel_timex *tx)
> err = ops->adjtime(ops, delta);
> } else if (tx->modes & ADJ_FREQUENCY) {
> long ppb = scaled_ppm_to_ppb(tx->freq);
> +
> if (ppb > ops->max_adj || ppb < -ops->max_adj)
> return -ERANGE;
> err = ops->adjfine(ops, tx->freq);
> @@ -278,11 +279,13 @@ struct ptp_clock *ptp_clock_register(struct ptp_clock_info *info,
> /* Register a new PPS source. */
> if (info->pps) {
> struct pps_source_info pps;
> +
> memset(&pps, 0, sizeof(pps));
> snprintf(pps.name, PPS_MAX_NAME_LEN, "ptp%d", index);
> pps.mode = PTP_PPS_MODE;
> pps.owner = info->owner;
> ptp->pps_source = pps_register_source(&pps, PTP_PPS_DEFAULTS);
> +
> if (IS_ERR(ptp->pps_source)) {
> err = PTR_ERR(ptp->pps_source);
> pr_err("failed to register pps source\n");
> @@ -347,9 +350,8 @@ static int unregister_vclock(struct device *dev, void *data)
>
> int ptp_clock_unregister(struct ptp_clock *ptp)
> {
> - if (ptp_vclock_in_use(ptp)) {
> + if (ptp_vclock_in_use(ptp))
> device_for_each_child(&ptp->dev, NULL, unregister_vclock);
> - }
>
> ptp->defunct = 1;
> wake_up_interruptible(&ptp->tsev_wq);
Two style fixes in one patch (blank lines and braces). Please split
them into each individual patches in a series.
But hey, shouldn't checkpatch complain about one-line brace block?
And also, the patch subject should have been [PATCH net-next]
(targetting next Linux release) or [PATCH net] (targetting current
release).
Thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-26 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 16:31 [PATCH] ptp: ptp_clock: Fix coding style issues Shinu Chandran
2023-03-26 7:47 ` Bagas Sanjaya [this message]
2023-03-28 0:47 ` Jakub Kicinski
2023-03-28 3:29 ` 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=ZB/4f0H0y8COVR90@debian.me \
--to=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=s4superuser@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.