From: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
To: valentina.manea.m@gmail.com, shuah@kernel.org, i@zenithal.me,
gregkh@linuxfoundation.org
Cc: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] usb/usbip : fixing warnings in stub_dev.c
Date: Sat, 16 Sep 2023 23:10:20 +0530 [thread overview]
Message-ID: <20230916174020.3218-1-bragathemanick0908@gmail.com> (raw)
Fix some checkpatch complaints in usb/usbip/stub_dev.c
Signed-off-by: Bragatheswaran Manickavel <bragathemanick0908@gmail.com>
---
drivers/usb/usbip/stub_dev.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/usbip/stub_dev.c b/drivers/usb/usbip/stub_dev.c
index 9c6954aad6c8..3a5771f74a3f 100644
--- a/drivers/usb/usbip/stub_dev.c
+++ b/drivers/usb/usbip/stub_dev.c
@@ -495,24 +495,25 @@ static void stub_disconnect(struct usb_device *udev)
busid_priv->status = STUB_BUSID_ADDED;
/* release busid_lock */
spin_unlock(&busid_priv->busid_lock);
- return;
}
#ifdef CONFIG_PM
-/* These functions need usb_port_suspend and usb_port_resume,
- * which reside in drivers/usb/core/usb.h. Skip for now. */
+/*
+ * These functions need usb_port_suspend and usb_port_resume,
+ * which reside in drivers/usb/core/usb.h. Skip for now.
+ */
static int stub_suspend(struct usb_device *udev, pm_message_t message)
{
- dev_dbg(&udev->dev, "stub_suspend\n");
+ dev_dbg(&udev->dev, "stub suspend\n");
return 0;
}
static int stub_resume(struct usb_device *udev, pm_message_t message)
{
- dev_dbg(&udev->dev, "stub_resume\n");
+ dev_dbg(&udev->dev, "stub resume\n");
return 0;
}
--
2.34.1
next reply other threads:[~2023-09-16 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 17:40 Bragatheswaran Manickavel [this message]
2023-09-16 19:17 ` [PATCH] usb/usbip : fixing warnings in stub_dev.c Greg KH
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=20230916174020.3218-1-bragathemanick0908@gmail.com \
--to=bragathemanick0908@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=i@zenithal.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=valentina.manea.m@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox