All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Tom Rini <trini@kernel.crashing.org>, Greg KH <greg@kroah.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2.6.12-rc4] Add EXPORT_SYMBOL for hotplug_path
Date: Fri, 20 May 2005 15:11:02 -0500	[thread overview]
Message-ID: <d120d500050520131118e42cc5@mail.gmail.com> (raw)
In-Reply-To: <1116618493.12975.48.camel@dhcp-188>

On 5/20/05, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Fri, 2005-05-20 at 14:07 -0500, Dmitry Torokhov wrote:
> > On 5/20/05, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > >
> > > Well, it doesn't depend on "make it private" it depends on Dimitry, who
> > > wanted to tweak our patch for the input layer. But we wait for weeeks
> > > for that. The SUSE kernel already ships a driver-core input layer
> > > without the /sbin/hotplug stuff.
> > >
> >
> > Kay,
> >
> > I am sorry for being slow with these patches but I really do spend all
> > time that I can on kernel.
> 
> Oh well, I know that problem. :) We need to move completely away from
> unmanaged kernel-forked processes in the hotplug area. SUSE 9.3 already
> ships a udevd that listens only on netlink for hotplug messages
> and /proc/sys/kernel/hotplug is set to "".
> Hannes converted the input layer to a input_device class to get the
> event through netlink. Maybe you can have a second look at it, so that
> we can get that thing upstream soon to fix the last broken hotplug-user
> and make hotplug_path finally private.
> 

Could you send me the tlatest version, please? Lats time I think there
were some concerns about lifetime rules...

-- 
Dmitry

      reply	other threads:[~2005-05-20 20:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 16:43 [PATCH 2.6.12-rc4] Add EXPORT_SYMBOL for hotplug_path Tom Rini
2005-05-19 17:40 ` Arjan van de Ven
2005-05-19 18:16   ` Tom Rini
2005-05-19 18:29     ` Dave Jones
2005-05-20  5:18 ` Greg KH
2005-05-20  5:18   ` Dmitry Torokhov
2005-05-20  5:37     ` Greg KH
2005-05-20  7:12 ` Kay Sievers
2005-05-20 17:18   ` Tom Rini
2005-05-20 17:56     ` Kay Sievers
2005-05-20 19:07       ` Dmitry Torokhov
2005-05-20 19:48         ` Kay Sievers
2005-05-20 20:11           ` 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=d120d500050520131118e42cc5@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.