From: Boris Brezillon <boris.brezillon@collabora.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Yoshio Furuyama <ytc-mb-yfuruyama7@kioxia.com>,
linux-mtd@lists.infradead.org, vigneshr@ti.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: Rename Toshiba Memory to Kioxia
Date: Tue, 28 Jan 2020 07:54:17 +0100 [thread overview]
Message-ID: <20200128075417.0fb68e10@collabora.com> (raw)
In-Reply-To: <20200127165148.1f8ef0f7@xps13>
On Mon, 27 Jan 2020 16:51:48 +0100
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hi Yoshio,
>
> Yoshio Furuyama <ytc-mb-yfuruyama7@kioxia.com> wrote on Thu, 23 Jan
> 2020 17:04:03 +0900:
>
> > Rename Toshiba Memory to Kioxia since the company name has changed.
>
> I wonder how much this is a noisy change compared to its benefits
>
> I would like more feedback. Richard, Boris, is this the first name we
> run into this situation? Ho was this handled in the past?
I don't think that's really useful. Maybe just add a comment above the
NAND_MFR_TOSHIBA definition stating that Toshiba and Kioxia ID are the
same. If Koxia starts producing new chip under the Koxia brand, new
files/structs/funcs/... can be prefixed with koxia instead of Toshiba.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Yoshio Furuyama <ytc-mb-yfuruyama7@kioxia.com>,
Richard Weinberger <richard.weinberger@gmail.com>,
linux-mtd@lists.infradead.org, vigneshr@ti.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: Rename Toshiba Memory to Kioxia
Date: Tue, 28 Jan 2020 07:54:17 +0100 [thread overview]
Message-ID: <20200128075417.0fb68e10@collabora.com> (raw)
In-Reply-To: <20200127165148.1f8ef0f7@xps13>
On Mon, 27 Jan 2020 16:51:48 +0100
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hi Yoshio,
>
> Yoshio Furuyama <ytc-mb-yfuruyama7@kioxia.com> wrote on Thu, 23 Jan
> 2020 17:04:03 +0900:
>
> > Rename Toshiba Memory to Kioxia since the company name has changed.
>
> I wonder how much this is a noisy change compared to its benefits
>
> I would like more feedback. Richard, Boris, is this the first name we
> run into this situation? Ho was this handled in the past?
I don't think that's really useful. Maybe just add a comment above the
NAND_MFR_TOSHIBA definition stating that Toshiba and Kioxia ID are the
same. If Koxia starts producing new chip under the Koxia brand, new
files/structs/funcs/... can be prefixed with koxia instead of Toshiba.
next prev parent reply other threads:[~2020-01-28 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 8:04 [PATCH] mtd: nand: Rename Toshiba Memory to Kioxia Yoshio Furuyama
2020-01-23 8:04 ` Yoshio Furuyama
2020-01-27 15:51 ` Miquel Raynal
2020-01-27 15:51 ` Miquel Raynal
2020-01-28 6:54 ` Boris Brezillon [this message]
2020-01-28 6:54 ` Boris Brezillon
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=20200128075417.0fb68e10@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard.weinberger@gmail.com \
--cc=vigneshr@ti.com \
--cc=ytc-mb-yfuruyama7@kioxia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.