From: Vineet Gupta <vgupta@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Matthew Wilcox <willy@infradead.org>, linux-snps-arc@lists.infradead.org
Subject: Re: [PATCH] ARC: thread_info.h: correct two typos in a comment
Date: Sat, 30 Oct 2021 10:34:00 -0700 [thread overview]
Message-ID: <a21e45ea-ebd4-6a1a-4508-2e2914603f7e@kernel.org> (raw)
In-Reply-To: <20211030003134.20553-1-rdunlap@infradead.org>
On 10/29/21 5:31 PM, Randy Dunlap wrote:
> Fix typos of "separately" and "remains".
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Suggested-by: Matthew Wilcox <willy@infradead.org> # "remains"
> Cc: Vineet Gupta <vgupta@kernel.org>
> Cc: linux-snps-arc@lists.infradead.org
Thx for the fix. Added to for-curr.
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
prev parent reply other threads:[~2021-10-30 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 0:31 [PATCH] ARC: thread_info.h: correct two typos in a comment Randy Dunlap
2021-10-30 17:34 ` Vineet Gupta [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=a21e45ea-ebd4-6a1a-4508-2e2914603f7e@kernel.org \
--to=vgupta@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=willy@infradead.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