From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
autofs mailing list <autofs@linux.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [PATCH] autofs4 - fix typo in expire-not-busy-only patch
Date: Wed, 18 Jan 2006 18:11:32 +0800 (WST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601181807480.9142@eagle.themaw.net> (raw)
Sorry, this error got through.
Signed-off-by: Ian Kent <raven@themaw.net>
--- linux-2.6.16-rc1/fs/autofs4/expire.c.expire-not-busy-only-fix 2006-01-18 17:55:15.000000000 +0800
+++ linux-2.6.16-rc1/fs/autofs4/expire.c 2006-01-18 17:56:28.000000000 +0800
@@ -255,11 +255,11 @@ static struct dentry *autofs4_expire(str
dentry, (int)dentry->d_name.len, dentry->d_name.name);
/* Can we umount this guy */
- if (autofs4_mount_busy(mnt, dentry)) {
+ if (autofs4_mount_busy(mnt, dentry))
goto next;
/* Can we expire this guy */
- if (autofs4_can_expire(dentry, timeout, do_now))
+ if (autofs4_can_expire(dentry, timeout, do_now)) {
expired = dentry;
break;
}
reply other threads:[~2006-01-18 10:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.64.0601181807480.9142@eagle.themaw.net \
--to=raven@themaw.net \
--cc=akpm@osdl.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).