From: "Rafał Miłecki" <zajec5@gmail.com>
To: Adrian Zaharia <Adrian.Zaharia@windriver.com>,
linux-mtd@lists.infradead.org
Cc: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
jani.nurminen@windriver.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/1] mtd: mtdpart: Fix cosmetic print
Date: Tue, 13 Sep 2022 09:37:21 +0200 [thread overview]
Message-ID: <43059215-aa56-e8c5-53a4-143643058797@gmail.com> (raw)
In-Reply-To: <20220825060407.335475-2-Adrian.Zaharia@windriver.com>
On 25.08.2022 08:04, Adrian Zaharia wrote:
> From: Jani Nurminen <jani.nurminen@windriver.com>
>
> The print of the MTD partitions during boot are off-by-one for the size.
> Fix this and show the real last offset.
I see that PCI subsystem and printk() + %pR do that. Probably more. I
guess it makes sense but I'm also wondering if/how confusing is that
change going to be for users. We did printing like that for probably
dozens of years.
> Fixes: 3d6f657ced2b ("mtd: mtdpart: Fix cosmetic print")
I can't find that hash / commit anywhere. Are you sure it exists?
> Signed-off-by: Jani Nurminen <jani.nurminen@windriver.com>
> Signed-off-by: Adrian Zaharia <Adrian.Zaharia@windriver.com>
> ---
> drivers/mtd/mtdpart.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/mtdpart.c b/drivers/mtd/mtdpart.c
> index d442fa94c872..fab10e6d4171 100644
> --- a/drivers/mtd/mtdpart.c
> +++ b/drivers/mtd/mtdpart.c
> @@ -118,7 +118,7 @@ static struct mtd_info *allocate_partition(struct mtd_info *parent,
> child->part.size = parent_size - child->part.offset;
>
> printk(KERN_NOTICE "0x%012llx-0x%012llx : \"%s\"\n",
> - child->part.offset, child->part.offset + child->part.size,
> + child->part.offset, child->part.offset + child->part.size - 1,
> child->name);
>
> /* let's do some sanity checks */
next prev parent reply other threads:[~2022-09-13 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 6:04 [PATCH 0/1] mtd: mtdpart: Fix cosmetic print Adrian Zaharia
2022-08-25 6:04 ` [PATCH 1/1] " Adrian Zaharia
2022-09-13 7:37 ` Rafał Miłecki [this message]
2022-09-19 15:57 ` Miquel Raynal
2022-09-13 5:25 ` [PATCH 0/1] " Rafał Miłecki
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=43059215-aa56-e8c5-53a4-143643058797@gmail.com \
--to=zajec5@gmail.com \
--cc=Adrian.Zaharia@windriver.com \
--cc=jani.nurminen@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--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