public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Wang Honghui <honghui.wang@139.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Correct syntax error
Date: Tue, 22 Nov 2022 14:56:57 +0700	[thread overview]
Message-ID: <Y3yAyQfCQjRlEV7n@debian.me> (raw)
In-Reply-To: <Y3w8JZjR5LygcClz@TP-P15V.lan>

[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]

On Tue, Nov 22, 2022 at 11:04:05AM +0800, Wang Honghui wrote:
> printk_ringbuffer.c

Welcome to LKML! If you want to contribute to Linux kernel, please
see Documentation/process/submitting-patches.rst.

> >From 8d1e2b96c62d06bb691802a06501762da606e97e Mon Sep 17 00:00:00 2001
> From: Wang Honghui <honghui.wang@139.com>
> Date: Mon, 21 Nov 2022 16:58:00 +0800
> Subject: [PATCH] Correct syntax error.
> 
> Signed-off-by: Wang Honghui <honghui.wang@139.com>
> ---
>  kernel/printk/printk_ringbuffer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/printk/printk_ringbuffer.c b/kernel/printk/printk_ringbuffer.c
> index 2b7b6ddab4f7..2dc4d5a1f1ff 100644
> --- a/kernel/printk/printk_ringbuffer.c
> +++ b/kernel/printk/printk_ringbuffer.c
> @@ -203,7 +203,7 @@
>   *	prb_rec_init_wr(&r, 5);
>   *
>   *	// try to extend, but only if it does not exceed 32 bytes
> - *	if (prb_reserve_in_last(&e, &test_rb, &r, printk_caller_id()), 32) {
> + *	if (prb_reserve_in_last(&e, &test_rb, &r, printk_caller_id(), 32)) {
>   *		snprintf(&r.text_buf[r.info->text_len],
>   *			 r.text_buf_size - r.info->text_len, "hello");
>   *
 
Your patch is attached, please send it inline using git-send-email(1)
instead. Use also scripts/get_maintainer.pl to determine appropriate
recipient for the patch.

Also, you need to describe about what and (especially important) why you
made the patch. Write it in imperative mood ("Do foo" instead of "This
patch/commit does foo").

Last but not least, build the kernel with your changes, preferably also
cross-compile it.

PS: I send this reply from mutt, which treats text attachments as inline
message body. Other MUAs may handle them differently.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2022-11-22  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22  3:04 Correct syntax error Wang Honghui
2022-11-22  7:56 ` Bagas Sanjaya [this message]

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=Y3yAyQfCQjRlEV7n@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=honghui.wang@139.com \
    --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