From: Roman Zippel <zippel@linux-m68k.org>
To: Andrew Morton <akpm@osdl.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] hfs: don't dirty unchanged inode
Date: Mon, 1 Aug 2005 11:49:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0508011146001.8800@scrub.home> (raw)
In-Reply-To: <Pine.LNX.4.61.0508011140440.8772@scrub.home>
Hi,
On Mon, 1 Aug 2005, Roman Zippel wrote:
> If inode size hasn't changed, don't do anything further in truncate, which
> also prevents a dirty inode, what might upset some readonly devices quite
> badly.
Sorry, I forgot this:
Signed-off-by: Roman Zippel <zippel@linux-m68k.org>
Andrew, the first two patches are also the most important and should go
into 2.6.13.
bye, Roman
prev parent reply other threads:[~2005-08-01 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 9:42 [PATCH 1/5] hfs: don't dirty unchanged inode Roman Zippel
2005-08-01 9:49 ` Roman Zippel [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=Pine.LNX.4.61.0508011146001.8800@scrub.home \
--to=zippel@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.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).