From: Boris Brezillon <boris.brezillon@bootlin.com>
To: IKEGAMI Tokunori <ikegami@allied-telesis.co.jp>
Cc: PACKHAM Chris <chris.packham@alliedtelesis.co.nz>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v7 5/5] mtd: cfi_cmdset_0002: Change erase one block to enable XIP once
Date: Wed, 30 May 2018 10:49:07 +0200 [thread overview]
Message-ID: <20180530104907.7b37cd05@bbrezillon> (raw)
In-Reply-To: <TY1PR01MB095408736BF00FE88D19AC13DC6D0@TY1PR01MB0954.jpnprd01.prod.outlook.com>
Hello,
On Tue, 29 May 2018 23:31:41 +0000
IKEGAMI Tokunori <ikegami@allied-telesis.co.jp> wrote:
> Hi Boris-san,
>
> Thanks for your reviewing and advices.
>
> > Is this really a bug fix? Doesn't look like a bug fix to me.
>
> No as you mentioned it is not a bug fix but just a refactoring to reduce xip_enable() line.
Then you should drop the Cc: stable tag.
>
> > Also, every time you add Cc stable you should try to find the commit
> > that introduced the bug. Sometime it's not possible because the bug
> > existed before git was in use, but most of the time you'll find the
> > offending commit using git blame.
> >
> > A fixes tag should be formatted like that:
> >
> > Fixes: <commit-id> ("commit subject")
>
> Okay I will do that in future.
>
> This is just FYI.
> I have just confirmed that the xip_enable() line itself was implemented by the commit 02b15e343aeef.
> For this patch it is not a bug fix so I will not add the Fixes line into the commit message.
Right.
> But if needed it please let me know that.
I checked the first patch and it seems it's one of these situation
where the code predates git, so no need to specify a Fixes tag.
Thanks,
Boris
next prev parent reply other threads:[~2018-05-30 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 23:27 [PATCH v7 0/5] mtd: cfi_cmdset_0002: Change write and erase functions Tokunori Ikegami
2018-05-27 23:27 ` [PATCH v7 1/5] mtd: cfi_cmdset_0002: Change write buffer to check correct value Tokunori Ikegami
2018-05-27 23:27 ` [PATCH v7 2/5] mtd: cfi_cmdset_0002: Change definition naming to retry write operation Tokunori Ikegami
2018-05-27 23:27 ` [PATCH v7 3/5] mtd: cfi_cmdset_0002: Change erase functions to retry for error Tokunori Ikegami
2018-05-27 23:28 ` [PATCH v7 4/5] mtd: cfi_cmdset_0002: Change erase functions to check chip good only Tokunori Ikegami
2018-05-27 23:28 ` [PATCH v7 5/5] mtd: cfi_cmdset_0002: Change erase one block to enable XIP once Tokunori Ikegami
2018-05-29 18:57 ` Boris Brezillon
2018-05-29 23:31 ` IKEGAMI Tokunori
2018-05-30 8:49 ` Boris Brezillon [this message]
2018-05-30 9:39 ` IKEGAMI Tokunori
2018-05-28 1:25 ` [PATCH v7 0/5] mtd: cfi_cmdset_0002: Change write and erase functions IKEGAMI Tokunori
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=20180530104907.7b37cd05@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=ikegami@allied-telesis.co.jp \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
/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