public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"jfs-discussion@lists.sourceforge.net" 
	<jfs-discussion@lists.sourceforge.net>
Subject: [GIT PULL] JFS updates for 3.11
Date: Wed, 10 Jul 2013 10:27:44 -0500	[thread overview]
Message-ID: <51DD7D70.5020307@oracle.com> (raw)

The following changes since commit 4d3797d7e1861ac1af150a6189315786c5e1c820:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-06-05 19:19:04 +0900)

are available in the git repository at:


  git://github.com/kleikamp/linux-shaggy.git tags/jfs-3.11

for you to fetch changes up to eb8630d7d2fd13589e6a7a3ae2fe1f75f867fbed:

  jfs: Update jfs_error (2013-06-05 14:47:19 -0500)

----------------------------------------------------------------
A couple cleanups to JFS for 3.11

----------------------------------------------------------------
Dave Kleikamp (1):
      jfs: fix sparse warning in fs/jfs/xattr.c

Joe Perches (1):
      jfs: Update jfs_error

 fs/jfs/jfs_dmap.c       | 70 +++++++++++++++++++------------------------------
 fs/jfs/jfs_dtree.c      | 37 +++++++++++++-------------
 fs/jfs/jfs_extent.c     |  2 +-
 fs/jfs/jfs_imap.c       | 69 ++++++++++++++++++++----------------------------
 fs/jfs/jfs_metapage.c   |  5 ++--
 fs/jfs/jfs_superblock.h |  1 +
 fs/jfs/jfs_txnmgr.c     |  2 +-
 fs/jfs/jfs_xtree.c      | 62 +++++++++++++++++++++----------------------
 fs/jfs/namei.c          |  2 +-
 fs/jfs/resize.c         |  2 +-
 fs/jfs/super.c          | 22 +++++++++-------
 fs/jfs/xattr.c          |  8 +++---
 12 files changed, 128 insertions(+), 154 deletions(-)

                 reply	other threads:[~2013-07-10 15:27 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=51DD7D70.5020307@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --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