From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Zhihao Cheng <chengzhihao1@huawei.com>
Cc: <richard@nod.at>, <vigneshr@ti.com>, <bbrezillon@kernel.org>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<yukuai3@huawei.com>
Subject: Re: [PATCH 1/2] mtd: mtdconcat: Judge callback function existence getting from master for each partition
Date: Sat, 7 Aug 2021 12:32:43 +0200 [thread overview]
Message-ID: <20210807123243.7661e4e3@xps13> (raw)
In-Reply-To: <27c67e42-f275-fc50-64e5-d80233130f7e@huawei.com>
Hi Zhihao,
Zhihao Cheng <chengzhihao1@huawei.com> wrote on Sat, 7 Aug 2021
10:15:46 +0800:
> 在 2021/8/7 3:28, Miquel Raynal 写道:
> Hi Miquel,
> > Hi Zhihao,
> >
> > Zhihao Cheng <chengzhihao1@huawei.com> wrote on Sat, 31 Jul 2021
> > 10:32:42 +0800:
> > @@ -721,14 +724,15 @@ struct mtd_info *mtd_concat_create(struct mtd_info *subdev[], /* subdevices to c
> > subdev[i]->flags & MTD_WRITEABLE;
> > }
> > > + subdev_master = mtd_get_master(subdev[i]);
> > concat->mtd.size += subdev[i]->size;
> > concat->mtd.ecc_stats.badblocks +=
> > subdev[i]->ecc_stats.badblocks;
> > if (concat->mtd.writesize != subdev[i]->writesize ||
> > concat->mtd.subpage_sft != subdev[i]->subpage_sft ||
> > concat->mtd.oobsize != subdev[i]->oobsize ||
> > - !concat->mtd._read_oob != !subdev[i]->_read_oob ||
> > - !concat->mtd._write_oob != !subdev[i]->_write_oob) {
> > + !concat->mtd._read_oob != !subdev_master->_read_oob ||
> > + !concat->mtd._write_oob != !subdev_master->_write_oob) {
> > Do you really need this change?
>
> I think both "!concat->mtd._read_oob != !subdev[i]->_read_oob" and "!concat->mtd._write_oob != !subdev[i]->_write_oob" need to be modified otherwise concatenating goes failure.
>
> I thought there exists two problems:
>
> 1. Wrong callback fetching in mtd partition device
>
> 2. Warning for existence of _read and _read_oob at the same time
>
> so I solved them in two steps to make history commit logs a bit clear.
>
> Though these two patches can be combined to one.
No please keep the split.
What I mean here is that I don't think your fix is valid. Maybe we
should propagate these callbacks as well instead of trying to hack into
this condition. I don't see why you should check against subdev[i] for
half of the callbacks and check for subdev_master for the last two.
Thanks,
Miquèl
next prev parent reply other threads:[~2021-08-07 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 2:32 [PATCH 0/2] mtd: mtdconcat: Fix callback functions check Zhihao Cheng
2021-07-31 2:32 ` [PATCH 1/2] mtd: mtdconcat: Judge callback function existence getting from master for each partition Zhihao Cheng
2021-08-06 19:28 ` Miquel Raynal
2021-08-07 2:15 ` Zhihao Cheng
2021-08-07 10:32 ` Miquel Raynal [this message]
2021-08-10 11:35 ` Zhihao Cheng
2021-08-16 13:43 ` Miquel Raynal
2021-08-16 14:27 ` Miquel Raynal
2021-07-31 2:32 ` [PATCH 2/2] mtd: mtdconcat: Remove concat_{read|write}_oob Zhihao Cheng
2021-08-06 19:26 ` Miquel Raynal
2021-08-07 2:59 ` Zhihao Cheng
2021-08-07 10:28 ` Miquel Raynal
2021-08-16 14:27 ` Miquel Raynal
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=20210807123243.7661e4e3@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=yukuai3@huawei.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