From: Dmitry Torokhov <dtor@insightbb.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [patch] input: function call order in serio_exit()
Date: Sun, 22 Oct 2006 23:15:47 -0400 [thread overview]
Message-ID: <200610222315.48592.dtor@insightbb.com> (raw)
In-Reply-To: <453B921D.80008@freemail.hu>
On Sunday 22 October 2006 11:45, Németh Márton wrote:
> Hi,
>
> the order of the bus registration and the kthread start was changed
> between linux kernel 2.6.17.11 and 2.6.18. The order is now first
> register the bus and then start the kthread. The serio_exit() left
> unchanged.
>
> I think that the order of the function calls in serio_exit() should also
> be changed: first stop the kthread and then unregister the bus.
>
> What do you think?
>
Hi,
It really does not matter - if bus is unregistered that means the there
are no drivers using it and so noone can submit new requests to kseriod.
I'd leave it as is.
--
Dmitry
prev parent reply other threads:[~2006-10-23 3:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 15:45 [patch] input: function call order in serio_exit() Németh Márton
2006-10-23 3:15 ` Dmitry Torokhov [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=200610222315.48592.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nm127@freemail.hu \
/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