Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: chengzhihao1 <chengzhihao1@huawei.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	 Miquel Raynal <miquel.raynal@bootlin.com>,
	 linux-mtd <linux-mtd@lists.infradead.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	 yi zhang <yi.zhang@huawei.com>
Subject: Re: [PATCH 0/6] ubifs: Fix wrong space calculation while doing budget
Date: Fri, 18 Nov 2022 09:56:28 +0100 (CET)	[thread overview]
Message-ID: <16338722.252938.1668761788563.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <8207d8f9-8b30-cfbb-9a5f-56294cb35601@huawei.com>

----- Ursprüngliche Mail -----
> Von: "chengzhihao1" <chengzhihao1@huawei.com>
> An: "richard" <richard@nod.at>, "Sascha Hauer" <s.hauer@pengutronix.de>, "Miquel Raynal" <miquel.raynal@bootlin.com>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>, "linux-kernel" <linux-kernel@vger.kernel.org>, "yi zhang"
> <yi.zhang@huawei.com>
> Gesendet: Freitag, 18. November 2022 09:53:38
> Betreff: Re: [PATCH 0/6] ubifs: Fix wrong space calculation while doing budget

> 在 2022/10/11 11:47, Zhihao Cheng 写道:
> 
> Hi. Richard
> Just a reminding. Could you please look through following series(Some of
> them is sent several months ago), I wish these can be merged in 6.1,
> thanks a lot:
> 
> ubi infinite loop:
> https://patchwork.ozlabs.org/project/linux-mtd/list/?series=304485
> ubi uaf in sysfs:
> https://patchwork.ozlabs.org/project/linux-mtd/list/?series=311956
> ubi fastmap:
> https://patchwork.ozlabs.org/project/linux-mtd/list/?series=313063
> ubifs assertion failed about writepage:
> https://patchwork.ozlabs.org/project/linux-mtd/list/?series=302776
> ubifs space budget:
> https://patchwork.ozlabs.org/project/linux-mtd/list/?series=322220

Sure. Let me check what happened to them.

Thanks,
//richard

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2022-11-18  8:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  3:47 [PATCH 0/6] ubifs: Fix wrong space calculation while doing budget Zhihao Cheng
2022-10-11  3:47 ` [PATCH 1/6] ubifs: Rectify space budget for ubifs_symlink() if symlink is encrypted Zhihao Cheng
2022-10-11  3:47 ` [PATCH 2/6] ubifs: Rectify space budget for ubifs_xrename() Zhihao Cheng
2022-10-11  3:47 ` [PATCH 3/6] ubifs: Add comments and debug info " Zhihao Cheng
2022-10-11  3:47 ` [PATCH 4/6] ubifs: Fix wrong dirty space budget for dirty inode Zhihao Cheng
2022-10-11  3:47 ` [PATCH 5/6] ubifs: do_rename: Fix wrong space budget when target inode's nlink > 1 Zhihao Cheng
2022-10-11  3:47 ` [PATCH 6/6] ubifs: Reserve one leb for each journal head while doing budget Zhihao Cheng
2022-11-18  8:53 ` [PATCH 0/6] ubifs: Fix wrong space calculation " Zhihao Cheng
2022-11-18  8:56   ` Richard Weinberger [this message]
2022-11-18  8:58     ` Zhihao Cheng

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=16338722.252938.1668761788563.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=chengzhihao1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=s.hauer@pengutronix.de \
    --cc=yi.zhang@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