public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.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 19:32:48 +0530	[thread overview]
Message-ID: <YB1QCHGUdDptkP0M@ArchLinux> (raw)
In-Reply-To: <20210205145716.4083e083@xps13>

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

On 14:57 Fri 05 Feb 2021, Miquel Raynal wrote:
>Hi Bhaskar,
>
>Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote on Fri, 5 Feb 2021
>19:06:39 +0530:
>
>> On 14:26 Fri 05 Feb 2021, Miquel Raynal wrote:
>> >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 *t
>> r)
>> >>  	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?
>> >
>> Got your point , and I do understand "fuck" and "fucking" is so strong word
>> that it is really difficult to replace with something else.
>>
>> But..but you suggestion to rewrite the comments sounds good Miquel ...wish I
>> could have that much time in hand to replace every sentence having that word
>> ...all the patched sent with that word replaces...please step forward and
>>  make
>> and send patches .
>>
>> Today I sent 10 patches replacing that word(weather that make sense or not)
>> you can see those in the ML ...please pick up as you wish and send patches.
>
>There are currently 21 uses of "fuck[ing]". It's not a mountain to
>climb. Nor a race.
>
✔ ~/git-linux/linux [master|✔]
19:28 $ search fuck | wc -l
15

>> I was simply replacing the word ..never bother about the meaning it
>> conveys..doesn't matter really.
>
>Are you kidding? What is the purpose of a comment if no one understands
>it after a blind change?
>
No I am not . But the sentences contains that word hardly have more meaning. But as you already said rewriting those comment would be a good idea...can you take up some of those??

>>
>> so...
>>

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

      reply	other threads:[~2021-02-05 23:54 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
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 [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=YB1QCHGUdDptkP0M@ArchLinux \
    --to=unixbhaskar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=rdunlap@infradead.org \
    --cc=richard@nod.at \
    --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