From: SF Markus Elfring <elfring@users.sourceforge.net>
To: kernel-janitors@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, trivial@kernel.org
Subject: [PATCH 2/5] misc/pti: Fix a typo in five comment lines
Date: Tue, 9 Jan 2018 19:29:44 +0100 [thread overview]
Message-ID: <0691f343-8160-02dd-0cac-83250bac4de4@users.sourceforge.net> (raw)
In-Reply-To: <bd359852-a809-280d-3d52-89216edc2058@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Tue, 9 Jan 2018 18:18:15 +0100
Adjust words in these descriptions.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/misc/pti.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/misc/pti.c b/drivers/misc/pti.c
index 92a1a20839c8..8292e8098cc8 100644
--- a/drivers/misc/pti.c
+++ b/drivers/misc/pti.c
@@ -378,7 +378,7 @@ EXPORT_SYMBOL_GPL(pti_release_masterchannel);
* @buf: Trace debuging data to write to the PTI HW.
* Null value will return with no write occurring.
* @count: Size of buf. Value of 0 or a negative number will
- * return with no write occuring.
+ * return with no write occurring.
*/
void pti_writedata(struct pti_masterchannel *mc, u8 *buf, int count)
{
@@ -403,7 +403,7 @@ EXPORT_SYMBOL_GPL(pti_writedata);
* ID to the PTI device via tty device.
*
* @tty: tty interface.
- * @filp: filp interface pased to tty_port_open() call.
+ * @filp: filp interface passed to tty_port_open() call.
*
* Returns:
* int, 0 for success
@@ -435,7 +435,7 @@ static int pti_tty_driver_open(struct tty_struct *tty, struct file *filp)
* master, channel aperture ID to the PTI device via tty device.
*
* @tty: tty interface.
- * @filp: filp interface pased to tty_port_close() call.
+ * @filp: filp interface passed to tty_port_close() call.
*
* The main purpose of using the tty device interface is to route
* syslog daemon messages to the PTI HW and out of the handheld platform
@@ -572,7 +572,7 @@ static int pti_char_open(struct inode *inode, struct file *filp)
* pti_char_release()- Close a char channel to the PTI device. Part
* of the misc device implementation.
*
- * @inode: Not used in this implementaiton.
+ * @inode: Not used in this implementation.
* @filp: Contains private_data that contains the master, channel
* ID to be released by the PTI device.
*
@@ -668,7 +668,7 @@ static struct miscdevice pti_char_driver = {
/**
* pti_console_write()- Write to the console that has been acquired.
*
- * @c: Not used in this implementaiton.
+ * @c: Not used in this implementation.
* @buf: Data to be written.
* @len: Length of buf.
*/
--
2.15.1
next prev parent reply other threads:[~2018-01-09 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 18:27 [PATCH 0/5] misc-PTI: Adjustments for some function implementations SF Markus Elfring
2018-01-09 18:28 ` [PATCH 1/5] misc/pti: Delete an error message for a failed memory allocation in two functions SF Markus Elfring
2018-01-09 18:29 ` SF Markus Elfring [this message]
2018-01-09 18:31 ` [PATCH 3/5] misc/pti: Improve a size determination " SF Markus Elfring
2018-01-09 18:32 ` [PATCH 4/5] misc/pti: Adjust 11 checks for null pointers SF Markus Elfring
2018-01-09 18:33 ` [PATCH 5/5] misc/pti: Delete an unnecessary return statement in two functions SF Markus Elfring
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=0691f343-8160-02dd-0cac-83250bac4de4@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/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
all inboxes | Powered by JetHome®