From: Artem Bityutskiy <dedekind1@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: [GIT PULL] UBIFS changes for v3.4-rc1
Date: Fri, 23 Mar 2012 15:40:21 +0200 [thread overview]
Message-ID: <1332510021.18717.65.camel@sauron.fi.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
Hi Linus,
The following changes since commit 6b21d18ed50c7d145220b0724ea7f2613abf0f95:
Linux 3.3-rc5 (2012-02-25 12:18:16 -0800)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-3.4-rc1
for you to fetch changes up to 5a1f36c90c9b21a7aa31c29a1926b376dd6a11cf:
UBIFS: improve error messages (2012-03-07 17:13:23 +0200)
----------------------------------------------------------------
- Improve error messages
- Clean-up i_nlink management
- Minor clean-ups
----------------------------------------------------------------
Artem Bityutskiy (6):
UBIFS: amend recovery debugging message
UBIFS: increase dumps loglevel
UBIFS: make the dbg_lock spinlock static
UBIFS: do not use inc_link when i_nlink is zero
UBIFS: kill CUR_MAX_KEY_LEN macro
UBIFS: improve error messages
fs/ubifs/debug.c | 410 +++++++++++++++++++++++++-------------------------
fs/ubifs/debug.h | 3 -
fs/ubifs/dir.c | 18 +-
fs/ubifs/recovery.c | 3 +-
fs/ubifs/sb.c | 19 ++-
fs/ubifs/ubifs.h | 11 +-
6 files changed, 234 insertions(+), 230 deletions(-)
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-03-23 13:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1332510021.18717.65.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®