The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, pmladek@suse.com,
	sergey.senozhatsky@gmail.com, rostedt@goodmis.org
Subject: Re: [PATCH] printk: fix typo in printk_safe.c
Date: Mon, 23 Oct 2017 13:07:21 +0900	[thread overview]
Message-ID: <20171023040721.GA426@tigerII.localdomain> (raw)
In-Reply-To: <1508682655-27293-1-git-send-email-bhe@redhat.com>

On (10/22/17 22:30), Baoquan He wrote:
> Signed-off-by: Baoquan He <bhe@redhat.com>

Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>

	-ss

> ---
>  kernel/printk/printk_safe.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/printk/printk_safe.c b/kernel/printk/printk_safe.c
> index 3cdaeaef9ce1..89558b85f45c 100644
> --- a/kernel/printk/printk_safe.c
> +++ b/kernel/printk/printk_safe.c
> @@ -75,7 +75,7 @@ static void queue_flush_work(struct printk_safe_seq_buf *s)
>   * have dedicated buffers, because otherwise printk-safe preempted by
>   * NMI-printk would have overwritten the NMI messages.
>   *
> - * The messages are fushed from irq work (or from panic()), possibly,
> + * The messages are flushed from irq work (or from panic()), possibly,
>   * from other CPU, concurrently with printk_safe_log_store(). Should this
>   * happen, printk_safe_log_store() will notice the buffer->len mismatch
>   * and repeat the write.
> -- 
> 2.5.5
> 

  reply	other threads:[~2017-10-23  4:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 14:30 [PATCH] printk: fix typo in printk_safe.c Baoquan He
2017-10-23  4:07 ` Sergey Senozhatsky [this message]
2017-10-30 14:51 ` Petr Mladek

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=20171023040721.GA426@tigerII.localdomain \
    --to=sergey.senozhatsky@gmail.com \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.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