public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Linus <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Please pull logfs tree for fixes
Date: Tue, 30 Mar 2010 09:22:36 +0200	[thread overview]
Message-ID: <20100330072236.GB11385@logfs.org> (raw)
In-Reply-To: <20100306210459.GA21570@logfs.org>

Good morning Linus!

I have a dozen fixes for you.  Some solve error path bugs, some are
necessary for the SSD that I never wanted to buy but finally did anyway
and the rest solve rather nasty bugs.

Al still has one error path problem I haven't dealt with yet.

 dev_bdev.c  |    9 +++++++--
 dir.c       |    4 ++--
 journal.c   |    7 +++++++
 logfs.h     |    1 +
 readwrite.c |   13 ++++++++++++-
 segment.c   |   54 +++++++++++++++++++++++++++++++-----------------------
 super.c     |   15 +++++++--------
 7 files changed, 67 insertions(+), 36 deletions(-)

git://git.kernel.org/pub/scm/linux/kernel/git/joern/logfs.git

Jörn

-- 
Joern's library part 11:
http://www.unicom.com/pw/reply-to-harmful.html

  parent reply	other threads:[~2010-03-30  7:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-06 21:04 Please pull logfs tree Jörn Engel
2010-03-06 21:26 ` Linus Torvalds
2010-03-06 21:35   ` Jörn Engel
2010-03-06 22:04     ` Linus Torvalds
2010-03-30  7:22 ` Jörn Engel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-21 12:19 Please pull logfs tree for fixes Jörn Engel
2010-04-21 14:09 ` Daniel Walker
2010-04-21 14:24   ` Jörn Engel
2010-05-17 17:19 Jörn Engel
2010-05-17 20:54 ` Linus Torvalds

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=20100330072236.GB11385@logfs.org \
    --to=joern@logfs.org \
    --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