From: Bhanusree Pola <bhanusreemahesh@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: gregkh@linuxfoundation.org
Subject: [Outreachy Kernel][PATCH v3] staging:comedi:comedi_pci.h Prefer a maximum 75 chars per line
Date: Sat, 6 Oct 2018 19:27:52 +0530 [thread overview]
Message-ID: <20181006135752.GA3037@veda-VGN-CS3AGH-R> (raw)
Adjust all lines exceeding 75 chars per line to fix checkpatch warning.
Signed-off-by: Bhanusree Pola <bhanusreemahesh@gmail.com>
---
changes in v4:
-Remove Whitespace in comment section of module_comedi_pci_driver()
to fix checkpatch Error.
changes in v3:
-Comment section of module_pci_driver() exceeds 75 characters.
Adjust the chars to 75 per line
-Modified log message.
-Added change log.
changes in v2:
-comedi_pci_auto_config() function prototype is exceeds
75 characters per line. Adjust to 75 chars to improve
readability and also adjust the arguments to match open
parantheses.
-Comment section of module_comedi_pci_driver() exceeds 75
characters. Modified contents to adjust 75 chars per line.
drivers/staging/comedi/comedi_pci.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/comedi_pci.h b/drivers/staging/comedi/comedi_pci.h
index 1cc5436cb415..7291d3c0b7dc 100644
--- a/drivers/staging/comedi/comedi_pci.h
+++ b/drivers/staging/comedi/comedi_pci.h
@@ -42,7 +42,7 @@ void comedi_pci_driver_unregister(struct comedi_driver *comedi_driver,
struct pci_driver *pci_driver);
/**
- * module_comedi_pci_driver()-Helper macro for registering a comedi PCI
+ * module_comedi_pci_driver()-Helper macro for registering a comedi PCI
* driver
* @__comedi_driver: comedi_driver struct
* @__pci_driver: pci_driver struct
--
2.17.1
next reply other threads:[~2018-10-06 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 13:57 Bhanusree Pola [this message]
2018-10-06 14:07 ` [Outreachy Kernel][PATCH v4] staging:comedi:comedi_pci.h Prefer a maximum 75 chars per line Bhanusree
2018-10-06 17:55 ` [Outreachy kernel] [Outreachy Kernel][PATCH v3] " Himanshu Jha
[not found] ` <68d61f32-294d-6056-7b3d-a89735bc539f@gmail.com>
[not found] ` <20181006180243.GG6283@himanshu-Vostro-3559>
2018-10-06 18:12 ` Bhanusree
2018-10-06 18:27 ` Himanshu Jha
2018-10-06 18:29 ` Bhanusree
2018-10-06 18:32 ` Himanshu Jha
2018-10-06 18:48 ` Bhanusree
2018-10-06 18:53 ` Julia Lawall
2018-10-06 17:59 ` Himanshu Jha
2018-10-06 18:05 ` Bhanusree
2018-10-06 18:13 ` Himanshu Jha
2018-10-06 18:15 ` Bhanusree
-- strict thread matches above, loose matches on Subject: below --
2018-10-06 13:28 [Outreachy kernel][PATCH " Bhanusree Pola
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=20181006135752.GA3037@veda-VGN-CS3AGH-R \
--to=bhanusreemahesh@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=outreachy-kernel@googlegroups.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.