From: Artem Bityutskiy <dedekind@infradead.org>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: UBIFS updates for 2.6.28
Date: Fri, 21 Nov 2008 19:19:22 +0200 [thread overview]
Message-ID: <1227287970-14684-1-git-send-email-dedekind@infradead.org> (raw)
Hi,
here are the UBIFS fixes we have scheduled for 2.6.28. We are
planning to send them to Linus a little bit later. I send them
for your review.
The "UBIFS: allow for gaps when dirtying the LPT" patch solves
the problem reported by Deepak Saxena.
The "UBIFS: remove printk" fixes a little bit annoying message
from UBIFS which comes every time we re-mount the FS.
The "UBIFS: do not print scary memory allocation warnings",
"UBIFS: do not allocate too much", and
"UBIFS: pre-allocate bulk-read buffer"
fix UBIFS memory allocation problems when bulk-read is enabled.
Adrian Hunter (1):
UBIFS: allow for gaps when dirtying the LPT
Artem Bityutskiy (6):
UBIFS: remove printk
MAINTAINERS: change UBI/UBIFS git tree URLs
UBIFS: fix compilation warnings
UBIFS: do not print scary memory allocation warnings
UBIFS: do not allocate too much
UBIFS: pre-allocate bulk-read buffer
Harvey Harrison (1):
UBIFS: endian handling fixes and annotations
MAINTAINERS | 4 +-
fs/ubifs/commit.c | 4 +-
fs/ubifs/debug.c | 66 +++++++++++++++++++++--------------
fs/ubifs/dir.c | 5 ++-
fs/ubifs/file.c | 91 ++++++++++++++++++++++++++++++++++---------------
fs/ubifs/journal.c | 8 +++--
fs/ubifs/key.h | 4 +-
fs/ubifs/lpt_commit.c | 2 -
fs/ubifs/orphan.c | 28 +++++++++------
fs/ubifs/recovery.c | 17 +++++----
fs/ubifs/replay.c | 2 +-
fs/ubifs/sb.c | 9 +++--
fs/ubifs/super.c | 70 +++++++++++++++++++++++++++++++------
fs/ubifs/tnc.c | 12 +++++--
fs/ubifs/ubifs.h | 12 +++++--
15 files changed, 223 insertions(+), 111 deletions(-)
--
Best regards,
Artem Bityutskiy (ÐиÑÑÑкий ÐÑÑÑм)
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-11-21 15:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 17:19 Artem Bityutskiy [this message]
2008-11-21 17:19 ` [PATCH] UBIFS: remove printk Artem Bityutskiy
2008-11-21 17:19 ` [PATCH] UBIFS: endian handling fixes and annotations Artem Bityutskiy
2008-11-22 19:27 ` Sebastian Andrzej Siewior
2008-11-23 3:21 ` Harvey Harrison
2008-11-23 9:28 ` Sebastian Andrzej Siewior
2008-11-23 10:05 ` Jamie Lokier
2008-11-24 14:19 ` Adrian Hunter
2008-11-24 16:46 ` Harvey Harrison
2008-12-02 9:12 ` Artem Bityutskiy
2008-11-21 17:19 ` [PATCH] MAINTAINERS: change UBI/UBIFS git tree URLs Artem Bityutskiy
2008-11-21 17:19 ` [PATCH] UBIFS: fix compilation warnings Artem Bityutskiy
2008-11-22 18:54 ` Sebastian Andrzej Siewior
2008-11-24 10:03 ` Adrian Hunter
2008-11-30 18:58 ` Sebastian Andrzej Siewior
2008-11-21 17:19 ` [PATCH] UBIFS: allow for gaps when dirtying the LPT Artem Bityutskiy
2008-11-21 17:19 ` [PATCH] UBIFS: do not print scary memory allocation warnings Artem Bityutskiy
2008-11-21 17:19 ` [PATCH] UBIFS: do not allocate too much Artem Bityutskiy
2008-11-21 17:19 ` [PATCH] UBIFS: pre-allocate bulk-read buffer Artem Bityutskiy
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=1227287970-14684-1-git-send-email-dedekind@infradead.org \
--to=dedekind@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).