mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] UBIFS changes for 2.6.31-rc3
Date: Thu, 09 Jul 2009 10:10:58 +0300	[thread overview]
Message-ID: <20090709071058.10124.94970.sendpatchset@localhost.localdomain> (raw)

Hi Linus,

here are UBIFS fixes for mount regression, compilation warnings,
recovery amendments and dumps.

Please, pull from:

git://git.infradead.org/ubifs-2.6.git linux-next

The following changes since commit 8e4a718ff38d8539938ec3421935904c27e00c39:
  Linus Torvalds (1):
        Linux 2.6.31-rc2

Adrian Hunter (3):
      UBIFS: fix integer overflow warning
      UBIFS: fix 64-bit divisions in debug print
      UBIFS: minor spelling and grammar fixes

Artem Bityutskiy (10):
      UBIFS: improve debugging messaged
      UBIFS: slightly optimize write-buffer timer usage
      UBIFS: set write-buffer timout to 3-5 seconds
      UBIFS: few spelling fixes
      UBIFS: fix assertion warning
      MAINTAINERS: update ahunter's e-mail address
      UBIFS: dump a little more in case of corruptions
      UBIFS: small amendments in the LEB scanning code
      UBIFS: clean up free space checking
      UBIFS: fix corruption dump

Daniel Mack (1):
      UBIFS: allow more than one volume to be mounted

 MAINTAINERS         |    2 +-
 fs/ubifs/io.c       |   57 ++++++++++++++++++++++++--------------------------
 fs/ubifs/recovery.c |   57 +++++++++++++++++++++++++++++---------------------
 fs/ubifs/replay.c   |    9 ++++---
 fs/ubifs/scan.c     |   20 ++++++++++-------
 fs/ubifs/super.c    |   14 +++++++-----
 fs/ubifs/ubifs.h    |   11 ++++++---
 7 files changed, 93 insertions(+), 77 deletions(-)

Thanks,
Artem.

                 reply	other threads:[~2009-07-09  5:21 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=20090709071058.10124.94970.sendpatchset@localhost.localdomain \
    --to=artem.bityutskiy@nokia.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome