From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org (open list:MEMORY TECHNOLOGY
DEVICES (MTD))
Subject: Re: [PATCH RFC 09/15] mtd: replace **** with a hug
Date: Fri, 30 Nov 2018 20:39:06 +0100 [thread overview]
Message-ID: <20181130203906.1af0d88d@bbrezillon> (raw)
In-Reply-To: <20181130192737.15053-10-jarkko.sakkinen@linux.intel.com>
On Fri, 30 Nov 2018 11:27:18 -0800
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
> In order to comply with the CoC, replace **** with a hug.
>
> Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.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 b0d44f9214b0..bdf68678fccc 100644
> --- a/drivers/mtd/mtd_blkdevs.c
> +++ b/drivers/mtd/mtd_blkdevs.c
> @@ -565,7 +565,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 hugging
> us over. */
Please rephrase the comment instead of this replacement.
> if (!blktrans_notifier.list.next)
> register_mtd_user(&blktrans_notifier);
next prev parent reply other threads:[~2018-11-30 19:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 19:27 [PATCH RFC 00/15] Zero ****s, hugload of hugs <3 Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 09/15] mtd: replace **** with a hug Jarkko Sakkinen
2018-11-30 19:39 ` Boris Brezillon [this message]
2018-11-30 20:56 ` Jarkko Sakkinen
2018-12-01 10:31 ` Richard Weinberger
2018-11-30 19:40 ` [PATCH RFC 00/15] Zero ****s, hugload of hugs <3 Kees Cook
2018-11-30 19:56 ` Davidlohr Bueso
2018-11-30 20:12 ` Jens Axboe
2018-11-30 20:34 ` Michael Schmitz
2018-11-30 20:35 ` David Miller
2018-11-30 21:42 ` Jarkko Sakkinen
2018-11-30 21:47 ` David Miller
2018-11-30 21:53 ` Jens Axboe
[not found] ` <2007856.n5V9iKLVsV@eth7>
2018-11-30 20:42 ` David Miller
2018-11-30 20:43 ` Steven Rostedt
2018-12-01 4:08 ` Jarkko Sakkinen
2018-11-30 20:34 ` David Miller
2018-11-30 20:55 ` Jarkko Sakkinen
2018-11-30 21:01 ` James Bottomley
2018-11-30 21:44 ` Jarkko Sakkinen
2018-11-30 21:48 ` David Miller
2018-11-30 21:54 ` Jarkko Sakkinen
2018-11-30 22:04 ` James Bottomley
2018-11-30 21:57 ` James Bottomley
2018-11-30 22:12 ` Jarkko Sakkinen
2018-11-30 22:14 ` Jonathan Corbet
2018-11-30 22:26 ` Jarkko Sakkinen
2018-11-30 22:29 ` Jarkko Sakkinen
2018-11-30 22:30 ` James Bottomley
2018-11-30 22:40 ` Jarkko Sakkinen
2018-11-30 23:28 ` Jarkko Sakkinen
2018-12-01 8:20 ` Geert Uytterhoeven
2018-12-07 13:39 ` Eric Curtin
2018-11-30 22:26 ` James Bottomley
2018-11-30 21:02 ` Steven Rostedt
2018-11-30 21:04 ` Jonathan Corbet
2018-11-30 20:09 ` John Paul Adrian Glaubitz
2018-11-30 21:32 ` Jarkko Sakkinen
2018-11-30 20:31 ` Matthias Brugger
2018-11-30 21:34 ` Jarkko Sakkinen
2018-11-30 20:42 ` Chris Mason
2018-11-30 21:36 ` Jarkko Sakkinen
2018-11-30 21:07 ` Jarkko Sakkinen
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=20181130203906.1af0d88d@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).