linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Burnicki <martin.burnicki@meinberg.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Need help to get udev/hotplug working for extra module	inearly2.6
Date: Thu, 17 Jul 2008 14:27:36 +0000	[thread overview]
Message-ID: <487F56D8.4090707@meinberg.de> (raw)
In-Reply-To: <4873789D.2080609@meinberg.de>

Greg,

Greg KH wrote:
> ..., we rely on the kernel to provide the events and act apon them,
> that's the whole point of the model.

Yes, however it may be possible that in recent kernels a certain kernel
API function e.g. class_device_create() creates a device object and also
generates an udev event whereas in older kernels you had to call 2
kernel API functions.

I'm maintaining our driver for many years now and remember the basic
improvements over the years, or limitations of older versions. Since
some of you guys here are also involved in the development of udev and
kernel drivers I was hoping someone could just give me a raw hint what
needed to be done with the older kernel API which isn't required nowadays.


Martin
-- 
Martin Burnicki

Meinberg Funkuhren
Bad Pyrmont
Germany

      parent reply	other threads:[~2008-07-17 14:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 14:24 Need help to get udev/hotplug working for extra module in early 2.6 Martin Burnicki
2008-07-15 10:21 ` Need help to get udev/hotplug working for extra module in early Martin Burnicki
2008-07-17  7:13 ` Need help to get udev/hotplug working for extra module in Greg KH
2008-07-17  8:38 ` Need help to get udev/hotplug working for extra module inearly Greg KH
2008-07-17 13:12 ` Need help to get udev/hotplug working for extra module Greg KH
2008-07-17 13:58 ` AW: Need help to get udev/hotplug working for extra module inearly2.6 Martin Burnicki
2008-07-17 14:27 ` Martin Burnicki [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=487F56D8.4090707@meinberg.de \
    --to=martin.burnicki@meinberg.de \
    --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).