From: Christoph Hellwig <hch@infradead.org>
To: Colin Leroy <colin@colino.net>
Cc: Roman Zippel <zippel@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] hfsplus: don't oops on bad FS
Date: Mon, 25 Apr 2005 21:07:04 +0100 [thread overview]
Message-ID: <20050425200704.GA16093@infradead.org> (raw)
In-Reply-To: <20050425220345.6b2ed6d5@jack.colino.net>
On Mon, Apr 25, 2005 at 10:03:45PM +0200, Colin Leroy wrote:
> + kfree((struct hfsplus_sb_info *)sb->s_fs_info);
absolutely no need to cast here.
next prev parent reply other threads:[~2005-04-25 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050425211915.126ddab5@jack.colino.net>
2005-04-25 19:53 ` [PATCH] hfsplus: don't oops on bad FS Roman Zippel
2005-04-25 20:03 ` Colin Leroy
2005-04-25 20:07 ` Christoph Hellwig [this message]
2005-04-25 20:12 ` Colin Leroy
2005-04-25 20:26 ` Roman Zippel
2005-04-26 6:59 ` Colin Leroy
2005-04-26 7:14 ` Colin Leroy
2005-04-25 20:29 ` Jesper Juhl
2005-05-01 5:08 ` Chris Wedgwood
2005-05-01 9:12 ` Colin Leroy
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=20050425200704.GA16093@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=colin@colino.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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