From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] drivers: mtd: Better word replace a not so good word in the file mtd_blkdevs.c
Date: Fri, 5 Feb 2021 14:26:18 +0100 [thread overview]
Message-ID: <20210205142618.116852a0@xps13> (raw)
In-Reply-To: <20210205124151.1386271-1-unixbhaskar@gmail.com>
Hi Bhaskar,
Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote on Fri, 5 Feb 2021
18:11:51 +0530:
> s/fucking/invite/
>
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> drivers/mtd/mtd_blkdevs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/mtd_blkdevs.c b/drivers/mtd/mtd_blkdevs.c
> index fb8e12d590a1..756a0995e474 100644
> --- a/drivers/mtd/mtd_blkdevs.c
> +++ b/drivers/mtd/mtd_blkdevs.c
> @@ -523,7 +523,7 @@ int register_mtd_blktrans(struct mtd_blktrans_ops *tr)
> int ret;
>
> /* Register the notifier if/when the first device type is
> - registered, to prevent the link/init ordering from fucking
> + registered, to prevent the link/init ordering from invite
> us over. */
invite us over?
I'm not a native English speaker but this does not bring any value to
my ears. Worse, I don't even get the point. Better rewrite the comment
entirely than just swapping "fucking" with a random word, no?
Thanks,
Miquèl
next prev parent reply other threads:[~2021-02-05 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 12:41 [PATCH] drivers: mtd: Better word replace a not so good word in the file mtd_blkdevs.c Bhaskar Chowdhury
2021-02-05 13:26 ` Miquel Raynal [this message]
2021-02-05 13:36 ` Bhaskar Chowdhury
2021-02-05 13:49 ` Richard Weinberger
2021-02-05 13:52 ` Bhaskar Chowdhury
2021-02-05 13:57 ` Miquel Raynal
2021-02-05 14:02 ` Bhaskar Chowdhury
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=20210205142618.116852a0@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=unixbhaskar@gmail.com \
--cc=vigneshr@ti.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