From: Ben Hutchings <ben.hutchings@essensium.com>
To: Zhihao Cheng <chengzhihao1@huawei.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/2] mtd: ubi: Fix some initialisation failure cases
Date: Thu, 11 Apr 2024 17:09:29 +0200 [thread overview]
Message-ID: <Zhf9KUCzO_bh_u38@cephalopod> (raw)
In-Reply-To: <f6191bef-9adb-9517-762d-ac95ebd3a4d1@huawei.com>
On Thu, Apr 11, 2024 at 11:30:41AM +0800, Zhihao Cheng wrote:
> 在 2024/4/11 6:42, Ben Hutchings 写道:
> > ubi currently fails to initialise if debugfs is enabled at build time
> > but disabled at boot time (CONFIG_DEBUG_FS is enabled and debugfs=off
> > is set on the kernel command line). Errors from debugfs should always
> > be ignored but this wasn't done everywhere.
> >
> > While fixing this I also noticed that a recent change to ubi removed
> > some cleanup from the ubi_init() failure path that I think is still
> > needed.
> >
> > This series should fix both problems.
> >
> > Ben.
>
> Hi, Ben. I have a same patch with your first one, I have merge our patchset
> into a new series [1]
> [1] https://lore.kernel.org/linux-mtd/20240411031903.3050278-1-chengzhihao1@huawei.com/
[...]
Thank you!
Ben.
--
Ben Hutchings · Senior Embedded Software Engineer, Essensium-Mind · mind.be
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2024-04-11 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 22:42 [PATCH 0/2] mtd: ubi: Fix some initialisation failure cases Ben Hutchings
2024-04-10 22:42 ` [PATCH 1/2] mtd: ubi: Restore missing cleanup on ubi_init() failure path Ben Hutchings
2024-04-10 22:42 ` [PATCH 2/2] mtd: ubi: Ignore all debugfs initialisation failures Ben Hutchings
2024-04-11 1:35 ` Zhihao Cheng
2024-04-11 3:30 ` [PATCH 0/2] mtd: ubi: Fix some initialisation failure cases Zhihao Cheng
2024-04-11 15:09 ` Ben Hutchings [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=Zhf9KUCzO_bh_u38@cephalopod \
--to=ben.hutchings@essensium.com \
--cc=chengzhihao1@huawei.com \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).