From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: autofs mailing list <autofs@linux.kernel.org>,
rhkernel-list@redhat.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] autofs4 - fix incorect return in autofs4_mount_busy()
Date: Thu, 23 Apr 2009 21:50:24 +0800 [thread overview]
Message-ID: <49F07220.2080004@themaw.net> (raw)
In-Reply-To: <20090423004523.7d4aee4a.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 23 Apr 2009 15:34:52 +0800 Ian Kent <raven@themaw.net> wrote:
>
>> This patch addresses bug 496766.
>
> In which tracking system?
>
> Please prefer to provide the full URL. I use the form:
>
> Addresses http://....496766
>
I'm asleep today, that was never meant for the public post, it refers to
a Redhat bug that has no additional information.
And there was no Signed-off-by, sorry, ;)
Ian
prev parent reply other threads:[~2009-04-23 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 7:34 [PATCH] autofs4 - fix incorect return in autofs4_mount_busy() Ian Kent
2009-04-23 7:45 ` Andrew Morton
2009-04-23 13:50 ` Ian Kent [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=49F07220.2080004@themaw.net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rhkernel-list@redhat.com \
/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).