linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: torvalds@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] hfsplus updates
Date: Fri, 7 Jan 2011 08:30:02 -0500	[thread overview]
Message-ID: <20110107133002.GA27044@infradead.org> (raw)

Hi Linus,

please pull the hfsplus updates for this merge window.  The most
important bits is fixing up fsync and sync to actually work correctly.
In addition to that hfsplus also stops using buffer heads for it's
superblock (volume header) as it needs to be accesses at 512 byte
granularity.  The rest is various small patches and a couple of cleanups
contributed by Anton.


The following changes since commit ff8b16d7e15a8ba2a6086645614a483e048e3fbf:

  vmstat: fix offset calculation on void* (2010-11-03 14:39:58 -0400)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/hch/hfsplus.git for-next

Anton Salikhmetov (5):
      hfsplus: fix an artifact in ioctl flag checking
      hfsplus: over 80 character lines clean-up
      hfsplus: C99 comments clean-up
      hfsplus: spaces/indentation clean-up
      hfsplus: %L-to-%ll, macro correction, and remove unneeded braces

Christoph Hellwig (12):
      hfsplus: fix option parsing during remount
      hfsplus: silence a few debug printks
      hfsplus: always use hfsplus_sync_fs to write the volume header
      hfsplus: use raw bio access for the volume headers
      hfsplus: use raw bio access for partition tables
      hfsplus: make sure sync writes out all metadata
      hfsplus: avoid useless work in hfsplus_sync_fs
      hfsplus: simplify fsync
      hfsplus: write up fsync for directories
      hfsplus: split up inode flags
      hfsplus: optimize fsync
      hfsplus: flush disk caches in sync and fsync

 fs/hfsplus/bfind.c       |    6 +-
 fs/hfsplus/bitmap.c      |    3 +-
 fs/hfsplus/bnode.c       |   70 +++++++++++-------
 fs/hfsplus/brec.c        |   28 +++++---
 fs/hfsplus/btree.c       |   33 ++++++---
 fs/hfsplus/catalog.c     |   85 ++++++++++++++--------
 fs/hfsplus/dir.c         |   37 +++++++---
 fs/hfsplus/extents.c     |   96 ++++++++++++++++---------
 fs/hfsplus/hfsplus_fs.h  |  125 +++++++++++++++++++-------------
 fs/hfsplus/hfsplus_raw.h |    3 +-
 fs/hfsplus/inode.c       |   89 +++++++++++++++--------
 fs/hfsplus/ioctl.c       |    6 +-
 fs/hfsplus/options.c     |   44 +++++++++++-
 fs/hfsplus/part_tbl.c    |  129 +++++++++++++++++++--------------
 fs/hfsplus/super.c       |  130 ++++++++++++++++++++-------------
 fs/hfsplus/unicode.c     |   41 +++++++----
 fs/hfsplus/wrapper.c     |  178 +++++++++++++++++++++++++++++-----------------
 17 files changed, 703 insertions(+), 400 deletions(-)

             reply	other threads:[~2011-01-07 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 13:30 Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-21  3:26 [GIT PULL] hfsplus updates Christoph Hellwig

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=20110107133002.GA27044@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).