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: Mon, 17 May 2010 19:19:29 +0200 [thread overview]
Message-ID: <20100517171929.GC28003@logfs.org> (raw)
Linus,
this should have made it into 2.6.34 - except that I was on vacation
last week and decided not to send a pull request right before hanging
out the "gone fishing" sign. Whether that was a wise decision, I'm no
longer so sure.
If such a situation reappears in the future, would you rather have the
fixes and mindlessly revert them in case of any trouble or wait until
the respective maintainer reappers?
Jörn
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
-- Brian W. Kernighan
The following changes since commit 79dba2eaa771c3173957eccfd288e0e0d12e4d3f:
Linus Torvalds (1):
Merge branch 'for-linus' of git://git.kernel.org/.../jbarnes/pci-2.6
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joern/logfs.git master
Dan Carpenter (2):
logfs: testing the wrong variable
logfs: handle errors from get_mtd_device()
Joern Engel (10):
LogFS: Fix typo in b6349ac8
logfs: Return -EINVAL if filesystem image doesn't match
logfs: fix logfs_seek_hole()
logfs: Close i_ino reuse race
logfs: survive logfs_buf_recover read errors
logfs: commit reservations under space pressure
logfs: fix compile failure
logfs: fix sync
logfs: remove unused variable
logfs: handle powerfail on NAND flash
Prasad Joshi (1):
logfs: initialize li->li_refcount
fs/logfs/dev_bdev.c | 6 ++++++
fs/logfs/dev_mtd.c | 26 +++++++++++++++++++++++++-
fs/logfs/file.c | 16 ++++++++++++----
fs/logfs/gc.c | 49 +++++++++++++++++++++----------------------------
fs/logfs/inode.c | 6 +++---
fs/logfs/journal.c | 7 +++----
fs/logfs/logfs.h | 13 ++++++++-----
fs/logfs/readwrite.c | 19 +++++++++++++++----
fs/logfs/segment.c | 7 +++++--
fs/logfs/super.c | 8 ++++++--
10 files changed, 104 insertions(+), 53 deletions(-)
next reply other threads:[~2010-05-17 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 17:19 Jörn Engel [this message]
2010-05-17 20:54 ` Please pull logfs tree for fixes Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2010-04-21 12:19 Jörn Engel
2010-04-21 14:09 ` Daniel Walker
2010-04-21 14:24 ` Jörn Engel
2010-03-06 21:04 Please pull logfs tree Jörn Engel
2010-03-30 7:22 ` Please pull logfs tree for fixes Jörn Engel
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=20100517171929.GC28003@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.