public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Hunter Adrian (Nokia-D/Helsinki)" <adrian.hunter@nokia.com>
Subject: Re: [GIT PULL] UBIFS changes for 2.6.30
Date: Sat, 04 Apr 2009 13:19:04 +0300	[thread overview]
Message-ID: <49D73418.6080209@nokia.com> (raw)
In-Reply-To: <49D20816.10506@nokia.com>

This seems to be forgotten.

Artem Bityutskiy wrote:
> Bityutskiy Artem (Nokia-D/Helsinki) wrote:
>> Hi Linus,
> 
> I'm sorry, one bugfix has been forgotten. Please,
> ignore the previous UBIFS pull request and take this
> one. It is the same but the "UBIFS: fix recovery bug"
> patch has been added.
> 
> The following changes since commit d5b562330ec766292a3ac54ae5e0673610bd5b3d:                                                           
>   Hugh Dickins (1):                                                                                                                    
>         mm: fix error case in mlock downgrade reversion                                                                                
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/ubifs-2.6.git linux-next
> 
> Adrian Hunter (3):
>       UBIFS: fix dbg_chk_lpt_sz()
>       UBIFS: fix bug where page is marked uptodate when out of space
>       UBIFS: fix recovery bug
> 
> Artem Bityutskiy (9):
>       UBIFS: improve find function interface
>       UBIFS: amend key_hash return value
>       UBIFS: fix bogus assertion
>       UBIFS: fix lprops committing bug
>       UBIFS: use KERN_CONT
>       UBIFS: introduce a helpful variable
>       UBIFS: fix commentaries
>       UBIFS: fully sort GCed nodes
>       UBIFS: add R/O compatibility
> 
> Eric Sesterhenn (1):
>       UBIFS: list usage cleanup
> 
> Hunter Adrian (1):
>       UBIFS: fix compiler warnings
> 
>  fs/ubifs/budget.c      |   37 ++---
>  fs/ubifs/debug.c       |    6 +-
>  fs/ubifs/file.c        |   16 ++-
>  fs/ubifs/find.c        |   12 +-
>  fs/ubifs/gc.c          |  428 +++++++++++++++++++++++++++++++++---------------
>  fs/ubifs/journal.c     |    7 +-
>  fs/ubifs/key.h         |    6 +-
>  fs/ubifs/log.c         |    5 +-
>  fs/ubifs/lpt_commit.c  |   34 ++--
>  fs/ubifs/recovery.c    |   70 +++------
>  fs/ubifs/replay.c      |    2 +-
>  fs/ubifs/sb.c          |   36 ++++-
>  fs/ubifs/shrinker.c    |    6 +-
>  fs/ubifs/super.c       |   37 +++-
>  fs/ubifs/tnc.c         |    2 +-
>  fs/ubifs/ubifs-media.h |   30 +++-
>  fs/ubifs/ubifs.h       |   13 +-
>  17 files changed, 482 insertions(+), 265 deletions(-)
> 

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2009-04-04 10:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 11:24 [GIT PULL] UBIFS changes for 2.6.30 Artem Bityutskiy
2009-03-31 12:09 ` Artem Bityutskiy
2009-04-04 10:19   ` Artem Bityutskiy [this message]

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=49D73418.6080209@nokia.com \
    --to=artem.bityutskiy@nokia.com \
    --cc=adrian.hunter@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