From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] use uevents in udevd
Date: Fri, 14 Jan 2005 13:35:09 +0000 [thread overview]
Message-ID: <1105709709.17412.60.camel@localhost.localdomain> (raw)
In-Reply-To: <41E79D7A.2060607@suse.de>
On Fri, 2005-01-14 at 14:11 +0100, Arnd Bergmann wrote:
> On Freedag 14 Januar 2005 14:12, Kay Sievers wrote:
> > On Fri, 2005-01-14 at 14:01 +0100, Arnd Bergmann wrote:
> > > On Freedag 14 Januar 2005 12:22, Hannes Reinecke wrote:
> > > > Martin promised that z90main will be fixed, so no worries about that
> > > > one. Will have to check pnpbios.
> > >
> > > I think z90crypt is clean already, because Z90CRYPT_USE_HOTPLUG is never
> > > defined anyway. The option is only there because the source used to be kept
> > > in sync with the 2.4 version.
So it should not hurt if we make hotplug_path private sometimes after
the input layer is converted. Good to know!
> > So how about using the right ifdef's then instead of this obfuscation.
>
> If I were maintaining that file, I'd simply throw out all the dead code.
Ah, ok.
> > And don't you want udev support for that device?
>
> AFAICS, it works fine with udev because it uses a miscdevice now, or am I
> missing something?
Yes, you are right.
Thanks,
Kay
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-01-14 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 10:22 [PATCH] use uevents in udevd Hannes Reinecke
2005-01-14 10:40 ` Marco d'Itri
2005-01-14 10:55 ` Hannes Reinecke
2005-01-14 10:55 ` Kay Sievers
2005-01-14 11:00 ` Marco d'Itri
2005-01-14 11:22 ` Hannes Reinecke
2005-01-14 11:26 ` Hannes Reinecke
2005-01-14 11:37 ` Marco d'Itri
2005-01-14 12:11 ` Kay Sievers
2005-01-14 12:43 ` Kay Sievers
2005-01-14 13:01 ` Arnd Bergmann
2005-01-14 13:01 ` Hannes Reinecke
2005-01-14 13:08 ` Kay Sievers
2005-01-14 13:11 ` Arnd Bergmann
2005-01-14 13:12 ` Kay Sievers
2005-01-14 13:23 ` Hannes Reinecke
2005-01-14 13:35 ` Kay Sievers [this message]
2005-01-14 16:08 ` Hannes Reinecke
2005-01-16 16:27 ` Kay Sievers
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=1105709709.17412.60.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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).