mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Jiangong.Han <jiangong.han@windriver.com>, <mingo@redhat.com>,
	<peterz@infradead.org>, <juri.lelli@redhat.com>,
	<vincent.guittot@linaro.org>
Cc: <dietmar.eggemann@arm.com>, <rostedt@goodmis.org>,
	<bsegall@google.com>, <mgorman@suse.de>, <vschneid@redhat.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: fix two misspellings.
Date: Mon, 20 Jul 2026 10:51:10 +0530	[thread overview]
Message-ID: <0abe2fa8-cea0-4bc8-bc31-93508f2080bc@amd.com> (raw)
In-Reply-To: <20260720010027.4020911-1-jiangong.han@windriver.com>

Please remove the "." at the end of the subject.

On 7/20/2026 6:30 AM, Jiangong.Han wrote:
> fix one misspelled word and one typo in function name.
> 
> Signed-off-by: Jiangong.Han <jiangong.han@windriver.com>

This should be your real name and not the email prefix
https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html#developer-s-certificate-of-origin-1-1

> ---
>  include/linux/sched.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 373bcc0598d1..7868663864ce 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -1790,7 +1790,7 @@ extern struct pid *cad_pid;
>  #define PF_NOFREEZE            0x00008000      /* This thread should not be frozen */
>  #define PF_KCOMPACTD           0x00010000      /* I am kcompactd */
>  #define PF_KSWAPD              0x00020000      /* I am kswapd */
> -#define PF_MEMALLOC_NOFS       0x00040000      /* All allocations inherit GFP_NOFS. See memalloc_nfs_save() */
> +#define PF_MEMALLOC_NOFS       0x00040000      /* All allocations inherit GFP_NOFS. See memalloc_nofs_save() */
>  #define PF_MEMALLOC_NOIO       0x00080000      /* All allocations inherit GFP_NOIO. See memalloc_noio_save() */
>  #define PF_LOCAL_THROTTLE      0x00100000      /* Throttle writes only against the bdi I write to,
>                                                  * I am cleaning dirty pages from some other bdi. */
> @@ -2377,7 +2377,7 @@ static __always_inline int task_mm_cid(struct task_struct *t)
>         /*
>          * Use the processor id as a fall-back when the mm cid feature is
>          * disabled. This provides functional per-cpu data structure accesses
> -        * in user-space, althrough it won't provide the memory usage benefits.
> +        * in user-space, although it won't provide the memory usage benefits.
>          */
>         return task_cpu(t);

For the change itself, feel free to include:

Reviewed-by: K Prateek Nayak <kprateek.nayak@amd.com>

>  }
> --
> 2.37.3
> 

-- 
Thanks and Regards,
Prateek


  reply	other threads:[~2026-07-20  5:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  1:00 Jiangong.Han
2026-07-20  5:21 ` K Prateek Nayak [this message]
2026-08-01 12:58   ` Jiangong.Han
2026-08-03  2:54   ` [PATCH][V3] " Jiangong.Han

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=0abe2fa8-cea0-4bc8-bc31-93508f2080bc@amd.com \
    --to=kprateek.nayak@amd.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jiangong.han@windriver.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /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®