From: Artem Bityutskiy <dedekind1@gmail.com>
To: ZhangJieJing <kzjeef@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [ubifs] add update vfs super block infomation when remount to ro mode.
Date: Thu, 08 Apr 2010 10:13:11 +0300 [thread overview]
Message-ID: <1270710791.6754.92.camel@localhost> (raw)
In-Reply-To: <r2icf7b913c1004080000t3f7c8c15yb6cea17f0d0496b1@mail.gmail.com>
Hi,
On Thu, 2010-04-08 at 15:00 +0800, ZhangJieJing wrote:
> If some read/write error happens(eg.CRC error), ubifs make self a read
> only mode,
> but the vfs infomation still not update.
> This patch add this also make /proc/mounts update.
>
> Signed-off-by: zhangjiejing <kzjeef@gmail.com>
>
> Change-Id: I709ada21d1f6168d2e785eac389510e2b5edb2a4
> ---
> fs/ubifs/io.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Could you please re-send this patch with CC to
linux-fsdevel@vger.kernel.org
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-04-08 7:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 7:00 [PATCH] [ubifs] add update vfs super block infomation when remount to ro mode ZhangJieJing
2010-04-08 7:13 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-16 3:36 [PATCH] ubifs: " ZhangJieJing
2010-04-16 3:36 ` ZhangJieJing
2010-04-16 19:10 ` Artem Bityutskiy
2010-04-16 19:10 ` Artem Bityutskiy
2010-04-28 7:24 ` Artem Bityutskiy
2010-04-28 7:24 ` Artem Bityutskiy
2010-04-29 2:14 ` Zhang JieJing
2010-04-29 2:14 ` Zhang JieJing
2010-04-29 3:46 ` Artem Bityutskiy
2010-04-29 3:46 ` Artem Bityutskiy
2010-04-29 6:36 ` Zhang JieJing
2010-04-29 6:36 ` Zhang JieJing
2010-04-29 6:44 ` Artem Bityutskiy
2010-04-29 6:44 ` Artem Bityutskiy
2010-04-29 6:38 ` Zhang JieJing
2010-04-29 6:38 ` Zhang JieJing
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=1270710791.6754.92.camel@localhost \
--to=dedekind1@gmail.com \
--cc=kzjeef@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.