[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171023040721.GA426@tigerII.localdomain>
Date: Mon, 23 Oct 2017 13:07:21 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Baoquan He <bhe@...hat.com>
Cc: linux-kernel@...r.kernel.org, pmladek@...e.com,
sergey.senozhatsky@...il.com, rostedt@...dmis.org
Subject: Re: [PATCH] printk: fix typo in printk_safe.c
On (10/22/17 22:30), Baoquan He wrote:
> Signed-off-by: Baoquan He <bhe@...hat.com>
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@...il.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
>
Powered by blists - more mailing lists