From: Vojtech Pavlik <vojtech@suse.cz>
To: Hannes Reinecke <hare@suse.de>
Cc: dtor_core@ameritech.net, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Remove input_call_hotplug
Date: Wed, 19 Jan 2005 16:49:46 +0100 [thread overview]
Message-ID: <20050119154946.GA8839@ucw.cz> (raw)
In-Reply-To: <41EE7521.1010900@suse.de>
On Wed, Jan 19, 2005 at 03:56:33PM +0100, Hannes Reinecke wrote:
> oops. hadn't thought of that. But of course, you are correct.
> So better be using monotonically increasing numbers.
>
> New patch attached.
This one looks quite OK to me.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-01-19 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 14:59 [PATCH 2/2] Remove input_call_hotplug Hannes Reinecke
2005-01-18 15:56 ` Dmitry Torokhov
2005-01-19 9:59 ` Hannes Reinecke
2005-01-19 14:05 ` Dmitry Torokhov
2005-01-19 14:16 ` Hannes Reinecke
2005-01-19 14:44 ` Dmitry Torokhov
2005-01-19 14:56 ` Hannes Reinecke
2005-01-19 15:49 ` Vojtech Pavlik [this message]
2005-01-19 15:50 ` Hannes Reinecke
2005-01-19 16:53 ` Vojtech Pavlik
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=20050119154946.GA8839@ucw.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=hare@suse.de \
--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