LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: shaggy@austin.ibm.com (Dave Kleikamp)
To: torvalds@osdl.org
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: [git pull] jfs update
Date: Mon,  2 Oct 2006 10:16:12 -0500 (CDT)	[thread overview]
Message-ID: <20061002151612.6AB5A83A2B@kleikamp.austin.ibm.com> (raw)

Linus, please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6.git for-linus

This will update the following files:

 fs/jfs/acl.c            |    8 -
 fs/jfs/endian24.h       |    2 
 fs/jfs/file.c           |    8 -
 fs/jfs/inode.c          |    8 -
 fs/jfs/jfs_acl.h        |    8 -
 fs/jfs/jfs_btree.h      |    6 -
 fs/jfs/jfs_debug.c      |    6 -
 fs/jfs/jfs_dinode.h     |    8 -
 fs/jfs/jfs_dmap.c       |  180 +++++++++++++++---------------
 fs/jfs/jfs_dmap.h       |   28 ++--
 fs/jfs/jfs_dtree.c      |   18 +--
 fs/jfs/jfs_dtree.h      |   10 -
 fs/jfs/jfs_extent.c     |   42 +++----
 fs/jfs/jfs_extent.h     |    8 -
 fs/jfs/jfs_filsys.h     |   24 ++--
 fs/jfs/jfs_imap.c       |  222 +++++++++++++++++++-------------------
 fs/jfs/jfs_imap.h       |   14 +-
 fs/jfs/jfs_incore.h     |    8 -
 fs/jfs/jfs_inode.c      |   15 +-
 fs/jfs/jfs_inode.h      |    6 -
 fs/jfs/jfs_lock.h       |   10 -
 fs/jfs/jfs_logmgr.c     |   38 +++---
 fs/jfs/jfs_logmgr.h     |   76 ++++++-------
 fs/jfs/jfs_metapage.c   |   12 +-
 fs/jfs/jfs_metapage.h   |    8 -
 fs/jfs/jfs_mount.c      |   34 ++---
 fs/jfs/jfs_superblock.h |   22 +--
 fs/jfs/jfs_txnmgr.c     |    8 -
 fs/jfs/jfs_txnmgr.h     |   12 +-
 fs/jfs/jfs_umount.c     |   24 ++--
 fs/jfs/jfs_unicode.c    |   12 +-
 fs/jfs/jfs_unicode.h    |   10 -
 fs/jfs/jfs_uniupr.c     |    8 -
 fs/jfs/jfs_xattr.h      |    2 
 fs/jfs/jfs_xtree.c      |   12 +-
 fs/jfs/jfs_xtree.h      |    8 -
 fs/jfs/namei.c          |   67 +++++------
 fs/jfs/resize.c         |    6 -
 fs/jfs/super.c          |   12 +-
 fs/jfs/symlink.c        |    6 -
 fs/jfs/xattr.c          |   38 +++---
 41 files changed, 525 insertions(+), 529 deletions(-)

through these ChangeSets:

Commit: 63f83c9fcf40ab61b75edf5d2f2c1ae6bf876482 
Author: Dave Kleikamp <shaggy@austin.ibm.com> Mon, 02 Oct 2006 09:55:27 -0500 

    JFS: White space cleanup
    
    Removed trailing spaces & tabs, and spaces preceding tabs.
    Also a couple very minor comment cleanups.
    
    Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
    (cherry picked from f74156539964d7b3d5164fdf8848e6a682f75b97 commit)

Commit: 087387f90f577f5a0ab68d33ef326c9bb6d80dda 
Author: Akinobu Mita <mita@miraclelinux.com> Thu, 14 Sep 2006 09:22:38 -0500 

    [PATCH] JFS: return correct error when i-node allocation failed
    
    I have seen confusing behavior on JFS when I injected many intentional
    slab allocation errors. The cp command failed with no disk space error
    with enough disk space.
    
    This patch makes:
    
    - change the return value in case slab allocation failures happen
      from -ENOSPC to -ENOMEM
    
    - ialloc() return error code so that the caller can know the reason
      of failures
    
    Signed-off-by: Akinobu Mita <mita@miraclelinux.com>
    Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
    (cherry picked from 2b46f77976f798f3fe800809a1d0ed38763c71c8 commit)

Commit: 2a6968a9784551c216f9379a728d4104dbad98a8 
Author: Tony Breeds <tony@bakeyournoodle.com> Mon, 11 Sep 2006 08:19:19 -0500 

    JFS: Remove shadow variable from fs/jfs/jfs_txnmgr.c:xtLog()
    
    Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
    Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
    (cherry picked from bdc3d9e5af7d9c105be734dd7b5c3f1d9425a15a commit)


             reply	other threads:[~2006-10-02 15:16 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 15:16 Dave Kleikamp [this message]
2006-10-02 15:31 ` Linus Torvalds
2006-10-02 15:41   ` Dave Kleikamp
2006-10-02 16:21     ` Al Viro
  -- strict thread matches above, loose matches on Subject: below --
2011-07-27 14:55 [GIT PULL] " Dave Kleikamp
2010-04-21 12:42 shaggy
2009-07-23 18:27 shaggy
2009-06-16 19:14 shaggy
2009-06-11 16:58 shaggy
2009-03-25 12:43 [git pull] " shaggy
2008-12-29 16:01 shaggy
2008-07-14 16:48 shaggy
2008-04-17 18:36 shaggy
2008-02-07 21:02 shaggy
2008-01-25 19:27 shaggy
2007-10-10 13:35 shaggy
2007-07-09 19:34 Dave Kleikamp
2007-05-08 14:51 Dave Kleikamp
2007-04-28 13:20 Dave Kleikamp
2007-02-14 23:08 Dave Kleikamp
2007-02-07 13:35 Dave Kleikamp
2006-12-12 15:16 Dave Kleikamp
2006-11-04  3:07 Dave Kleikamp
2006-11-02 14:23 Dave Kleikamp
2006-10-23 12:53 Dave Kleikamp
2006-09-25 13:04 Dave Kleikamp
2006-08-03 14:37 Dave Kleikamp
2006-07-14  1:45 Dave Kleikamp
2006-07-06 14:20 Dave Kleikamp
2006-05-24 13:10 Dave Kleikamp
2006-03-20 14:57 Dave Kleikamp
2006-03-14 18:47 Dave Kleikamp
2006-03-14 19:33 ` Linus Torvalds
2005-11-09 21:40 Dave Kleikamp
2005-10-28 19:12 Dave Kleikamp
2005-08-04 21:07 Dave Kleikamp
2005-07-27 18:05 Dave Kleikamp
2005-07-27 23:43 ` Linus Torvalds
2005-07-13 14:41 Dave Kleikamp
2005-06-20 16:18 Dave Kleikamp
2005-05-04 20:47 Dave Kleikamp
2005-05-04 21:37 ` Linus Torvalds
2005-05-05 18:16   ` Jeff Garzik
2005-05-05 18:22     ` Linus Torvalds
2005-05-05 18:51       ` Dave Kleikamp
2005-05-05 19:39         ` Andrew Morton
2005-05-06 19:13           ` Dave Kleikamp

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=20061002151612.6AB5A83A2B@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --subject='Re: [git pull] jfs update' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).