From: "Petr Mládek" <pmladek@suse.cz>
To: Alex Elder <elder@linaro.org>
Cc: akpm@linux-foundation.org, bp@suse.de, john.stultz@linaro.org,
jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] printk: correct some more typos
Date: Fri, 18 Jul 2014 13:46:22 +0200 [thread overview]
Message-ID: <20140718114621.GB6774@pathway.suse.cz> (raw)
In-Reply-To: <1405606151-19875-7-git-send-email-elder@linaro.org>
On Thu 2014-07-17 09:09:11, Alex Elder wrote:
> This patch corrects a few more typographical errors in "printk.c".
>
> Signed-off-by: Alex Elder <elder@linaro.org>
Reviewed-by: Petr Mladek <pmladek@suse.cz>
Best Regards,
Petr
> ---
> kernel/printk/printk.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 3174ba9..eff68a4 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -201,7 +201,7 @@ static int console_may_schedule;
> *
> * The optional key/value pairs are attached as continuation lines starting
> * with a space character and terminated by a newline. All possible
> - * non-prinatable characters are escaped in the "\xff" notation.
> + * non-printable characters are escaped in the "\xff" notation.
> *
> * Users of the export format should ignore possible additional values
> * separated by ',', and find the message after the ';' character.
> @@ -615,7 +615,7 @@ static ssize_t devkmsg_read(struct file *file, char __user *buf,
> /*
> * If we couldn't merge continuation line fragments during the print,
> * export the stored flags to allow an optional external merge of the
> - * records. Merging the records isn't always neccessarily correct, like
> + * records. Merging the records isn't always necessarily correct, like
> * when we hit a race during printing. In most cases though, it produces
> * better readable output. 'c' in the record flags mark the first
> * fragment of a line, '+' the following.
> @@ -2890,7 +2890,7 @@ bool kmsg_dump_get_buffer(struct kmsg_dumper *dumper, bool syslog,
> prev = msg->flags;
> }
>
> - /* last message in next interation */
> + /* last message in next iteration */
> next_seq = seq;
> next_idx = idx;
>
> @@ -2916,7 +2916,7 @@ out:
> EXPORT_SYMBOL_GPL(kmsg_dump_get_buffer);
>
> /**
> - * kmsg_dump_rewind_nolock - reset the interator (unlocked version)
> + * kmsg_dump_rewind_nolock - reset the iterator (unlocked version)
> * @dumper: registered kmsg dumper
> *
> * Reset the dumper's iterator so that kmsg_dump_get_line() and
> @@ -2934,7 +2934,7 @@ void kmsg_dump_rewind_nolock(struct kmsg_dumper *dumper)
> }
>
> /**
> - * kmsg_dump_rewind - reset the interator
> + * kmsg_dump_rewind - reset the iterator
> * @dumper: registered kmsg dumper
> *
> * Reset the dumper's iterator so that kmsg_dump_get_line() and
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-07-18 11:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 14:09 [PATCH v2 0/6] printk: start simplifying some flags Alex Elder
2014-07-17 14:09 ` [PATCH v2 1/6] printk: initialize syslog_prev and console_prev Alex Elder
2014-07-18 10:43 ` Petr Mládek
2014-07-18 13:38 ` Alex Elder
2014-07-17 14:09 ` [PATCH v2 2/6] printk: LOG_CONT and LOG_NEWLINE are opposites Alex Elder
2014-07-18 10:53 ` Petr Mládek
2014-07-18 13:39 ` Alex Elder
2014-07-17 14:09 ` [PATCH v2 3/6] printk: honor LOG_PREFIX in devkmsg_read() Alex Elder
2014-07-17 14:09 ` [PATCH v2 4/6] printk: honor LOG_PREFIX in msg_print_text() Alex Elder
2014-07-18 11:03 ` Petr Mládek
2014-07-17 14:09 ` [PATCH v2 5/6] printk: insert newline in devkmsg_read() Alex Elder
2014-07-18 11:45 ` Petr Mládek
2014-07-18 14:02 ` Alex Elder
2014-07-17 14:09 ` [PATCH v2 6/6] printk: correct some more typos Alex Elder
2014-07-18 11:46 ` Petr Mládek [this message]
2014-07-17 15:59 ` [PATCH v2 0/6] printk: start simplifying some flags Joe Perches
2014-07-17 16:04 ` Alex Elder
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=20140718114621.GB6774@pathway.suse.cz \
--to=pmladek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=elder@linaro.org \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.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®