From: Boris Brezillon <boris.brezillon@collabora.com>
To: Joel Stanley <joel@jms.id.au>
Cc: linuxppc-dev@lists.ozlabs.org,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: powernv: SPDX and comment fixups
Date: Thu, 7 Feb 2019 09:37:34 +0100 [thread overview]
Message-ID: <20190207093734.400875cd@collabora.com> (raw)
In-Reply-To: <20190206003659.27107-1-joel@jms.id.au>
Hello Joel,
On Wed, 6 Feb 2019 11:06:58 +1030
Joel Stanley <joel@jms.id.au> wrote:
> This converts the powernv flash driver to use SPDX, and adds some
> clarifying comments that came out of a discussion on how the mtd driver
> works.
Can you split that in 2 patches, one adding the SPDX header, and the
other one clarifying the driver behavior.
Thanks,
Boris
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
> ---
> drivers/mtd/devices/powernv_flash.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/mtd/devices/powernv_flash.c b/drivers/mtd/devices/powernv_flash.c
> index 22f753e555ac..0bf43336c3f7 100644
> --- a/drivers/mtd/devices/powernv_flash.c
> +++ b/drivers/mtd/devices/powernv_flash.c
> @@ -1,17 +1,9 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +
> /*
> * OPAL PNOR flash MTD abstraction
> *
> * Copyright IBM 2015
> - *
> - * This program is free software; you can redistribute it and/or modify
> - * it under the terms of the GNU General Public License as published by
> - * the Free Software Foundation; either version 2 of the License, or
> - * (at your option) any later version.
> - *
> - * This program is distributed in the hope that it will be useful,
> - * but WITHOUT ANY WARRANTY; without even the implied warranty of
> - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> - * GNU General Public License for more details.
> */
>
> #include <linux/kernel.h>
> @@ -261,6 +253,14 @@ static int powernv_flash_probe(struct platform_device *pdev)
> * The current flash that skiboot exposes is one contiguous flash chip
> * with an ffs partition at the start, it should prove easier for users
> * to deal with partitions or not as they see fit
> + *
> + * When developing the skiboot MTD driver an experiment with FFS
> + * parsing in the kernel, and exposing a seperate /dev/mtdX for each
> + * partition (eg BOOTKERNEL, PAYLOAD, NVRAM, etc), was done.
> + *
> + * We didn't go with that as it meant users couldn't do a full flash
> + * re-write, as this can cause a partition to change size, and there
> + * wasn't a way to tell the MTD layer that a device has shrunk/grown.
> */
> return mtd_device_register(&data->mtd, NULL, 0);
> }
prev parent reply other threads:[~2019-02-07 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 0:36 [PATCH] mtd: powernv: SPDX and comment fixups Joel Stanley
2019-02-06 1:08 ` Stewart Smith
2019-02-07 8:37 ` Boris Brezillon [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=20190207093734.400875cd@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=joel@jms.id.au \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.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).