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 regression fixes
Date: Tue, 5 Jul 2011 06:44:14 -0400 [thread overview]
Message-ID: <20110705104414.GA17713@infradead.org> (raw)
Hi Linus,
please pull two small fixes for regressions introduced in the last
big batch of hfsplus updates in 2.6.38.
The following changes since commit ca56a95eedcc95f8fea7b49c87565cd961d74fe2:
Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 (2011-06-29 18:18:48 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/hch/hfsplus.git for-linus
Alexey Khoroshilov (1):
hfsplus: Fix double iput of the same inode in hfsplus_fill_super()
Seth Forshee (1):
hfsplus: add missing call to bio_put()
fs/hfsplus/super.c | 2 +-
fs/hfsplus/wrapper.c | 7 +++++--
2 files changed, 6 insertions(+), 3 deletions(-)
next reply other threads:[~2011-07-05 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 10:44 Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-04 0:23 [GIT PULL] hfsplus regression fixes 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=20110705104414.GA17713@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).