From: Johannes Berg <johannes@sipsolutions.net>
To: wangjianli <wangjianli@cdjrlc.com>,
richard@nod.at, anton.ivanov@cambridgegreys.com
Cc: linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] um/kernel: fix repeated words in comments
Date: Thu, 08 Sep 2022 14:56:03 +0200 [thread overview]
Message-ID: <514c7366cc8e78face3094a66bb2c4bf030f9432.camel@sipsolutions.net> (raw)
In-Reply-To: <20220908125401.28130-1-wangjianli@cdjrlc.com>
On Thu, 2022-09-08 at 20:54 +0800, wangjianli wrote:
> Delete the redundant word 'in'.
>
> Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
> ---
> arch/um/kernel/physmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/um/kernel/physmem.c b/arch/um/kernel/physmem.c
> index e7c7b53a1435..91485119ae67 100644
> --- a/arch/um/kernel/physmem.c
> +++ b/arch/um/kernel/physmem.c
> @@ -169,7 +169,7 @@ __uml_setup("iomem=", parse_iomem,
> );
>
> /*
> - * This list is constructed in parse_iomem and addresses filled in in
> + * This list is constructed in parse_iomem and addresses filled in
> * setup_iomem, both of which run during early boot. Afterwards, it's
>
Fine, I guess, but honestly - that sentence doesn't parse well either
way. Might be worth addressing that at the same time...
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2022-09-08 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 12:54 [PATCH] um/kernel: fix repeated words in comments wangjianli
2022-09-08 12:56 ` Johannes Berg [this message]
2022-09-08 17:45 ` Geert Uytterhoeven
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=514c7366cc8e78face3094a66bb2c4bf030f9432.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=wangjianli@cdjrlc.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