From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: torvalds@transmeta.com
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ncpfs seems to need the timer init
Date: Tue, 26 Nov 2002 14:53:22 +0100 [thread overview]
Message-ID: <20021126135322.GA30362@vana> (raw)
In-Reply-To: <200211260411.gAQ4BUo24135@hera.kernel.org>
On Tue, Nov 26, 2002 at 02:12:52AM +0000, Linux Kernel Mailing List wrote:
Linus, please revert this. It is changeset
alan@lxorguk.ukuu.org.uk|ChangeSet|20021126021252|43411
Timer is already initialized few lines above in the code. If you'll look
through fs/ncpfs/inode.c history, you'll find that I already asked once
for removing this redundant timer initialization, but unfortunately it
found its way to the tree again :-(
I prefer having init_timer() and timeout_tm setup separate, as now
I can safely call del_timer in shutdown without having to test
whether I'm in UDP or TCP code...
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
> ChangeSet 1.842.42.99, 2002/11/25 18:12:52-08:00, alan@lxorguk.ukuu.org.uk
>
> [PATCH] ncpfs seems to need the timer init
>
>
> # This patch includes the following deltas:
> # ChangeSet 1.842.42.98 -> 1.842.42.99
> # fs/ncpfs/inode.c 1.36 -> 1.37
> #
>
> inode.c | 1 +
> 1 files changed, 1 insertion(+)
>
>
> diff -Nru a/fs/ncpfs/inode.c b/fs/ncpfs/inode.c
> --- a/fs/ncpfs/inode.c Mon Nov 25 20:11:32 2002
> +++ b/fs/ncpfs/inode.c Mon Nov 25 20:11:32 2002
> @@ -575,6 +575,7 @@
> } else {
> INIT_WORK(&server->rcv.tq, ncpdgram_rcv_proc, server);
> INIT_WORK(&server->timeout_tq, ncpdgram_timeout_proc, server);
> + init_timer(&server->timeout_tm);
> server->timeout_tm.data = (unsigned long)server;
> server->timeout_tm.function = ncpdgram_timeout_call;
> }
next parent reply other threads:[~2002-11-26 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200211260411.gAQ4BUo24135@hera.kernel.org>
2002-11-26 13:53 ` Petr Vandrovec [this message]
2002-11-26 14:35 ` Alan Cox
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=20021126135322.GA30362@vana \
--to=vandrove@vc.cvut.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®