From: Carlos Llamas <cmllamas@google.com>
To: Richard Cochran <richardcochran@gmail.com>,
"David S. Miller" <davem@davemloft.net>
Cc: Yang Yingliang <yangyingliang@huawei.com>,
netdev@vger.kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org, Carlos Llamas <cmllamas@google.com>
Subject: [PATCH net] ptp: fix code indentation issues
Date: Wed, 27 Oct 2021 23:18:02 +0000 [thread overview]
Message-ID: <20211027231802.2844313-1-cmllamas@google.com> (raw)
This fixes the following checkpatch.pl errors:
ERROR: code indent should use tabs where possible
+^I if (ptp->pps_source)$
ERROR: code indent should use tabs where possible
+^I pps_unregister_source(ptp->pps_source);$
ERROR: code indent should use tabs where possible
+^I kthread_destroy_worker(ptp->kworker);$
Fixes: 4225fea1cb28 ("ptp: Fix possible memory leak in ptp_clock_register()")
Signed-off-by: Carlos Llamas <cmllamas@google.com>
---
drivers/ptp/ptp_clock.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/ptp/ptp_clock.c b/drivers/ptp/ptp_clock.c
index f9b2d66b0443..0e4bc8b9329d 100644
--- a/drivers/ptp/ptp_clock.c
+++ b/drivers/ptp/ptp_clock.c
@@ -284,11 +284,11 @@ struct ptp_clock *ptp_clock_register(struct ptp_clock_info *info,
/* Create a posix clock and link it to the device. */
err = posix_clock_register(&ptp->clock, &ptp->dev);
if (err) {
- if (ptp->pps_source)
- pps_unregister_source(ptp->pps_source);
+ if (ptp->pps_source)
+ pps_unregister_source(ptp->pps_source);
if (ptp->kworker)
- kthread_destroy_worker(ptp->kworker);
+ kthread_destroy_worker(ptp->kworker);
put_device(&ptp->dev);
--
2.33.0.1079.g6e70778dc9-goog
next reply other threads:[~2021-10-27 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 23:18 Carlos Llamas [this message]
2021-10-28 13:50 ` [PATCH net] ptp: fix code indentation issues patchwork-bot+netdevbpf
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=20211027231802.2844313-1-cmllamas@google.com \
--to=cmllamas@google.com \
--cc=davem@davemloft.net \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=yangyingliang@huawei.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.