From: Christoph Hellwig <hch@infradead.org>
To: torvalds@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] hfsplus fixes for Linux 3.5
Date: Sun, 17 Jun 2012 17:09:29 -0400 [thread overview]
Message-ID: <20120617210929.GA29127@infradead.org> (raw)
In-Reply-To: <20120617210523.088906451@bombadil.infradead.org>
On Sun, Jun 17, 2012 at 05:05:23PM -0400, Christoph Hellwig wrote:
> Two small hfsplus fixes:
>
> - a one liner regression fix for large volume handling from
Sorry, chopped off the message, should be:
Two small hfsplus fixes:
- a one liner regression fix for large volume handling from
Janne Kalliom??ki.
- a fixup for the boot image blessing feature to make it work
with the fake "hardlinks" in hfsplus from Matthew Garrett.
prev parent reply other threads:[~2012-06-17 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 21:05 [PATCH 0/2] hfsplus fixes for Linux 3.5 Christoph Hellwig
2012-06-17 21:05 ` [PATCH 1/2] hfsplus: fix overflow in sector calculations in hfsplus_submit_bio Christoph Hellwig
2012-06-17 21:05 ` [PATCH 2/2] hfsplus: fix bless ioctl when used with hardlinks Christoph Hellwig
2012-06-17 21:09 ` Christoph Hellwig [this message]
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=20120617210929.GA29127@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).