From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] uinput: add devname alias to allow module on-demand load
Date: Sun, 19 Sep 2010 16:27:51 -0700 [thread overview]
Message-ID: <20100919232751.GB6565@core.coreip.homeip.net> (raw)
In-Reply-To: <AANLkTinFjnt7zm3YmOAASR6YEn+6CSWcbNV3R4=scnSh@mail.gmail.com>
On Fri, Sep 17, 2010 at 06:59:24PM +0200, Kay Sievers wrote:
> On Fri, Sep 17, 2010 at 18:05, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > On Fri, Sep 17, 2010 at 11:53:43AM +0200, Kay Sievers wrote:
> >> On Thu, Aug 19, 2010 at 14:58, Kay Sievers <kay.sievers@vrfy.org> wrote:
> >> > From: Kay Sievers <kay.sievers@vrfy.org>
> >> > Subject: uinput: add devname alias to allow module on-demand load
> >> >
> >> > Recent modprobe and udev versions allow to create device nodes
> >> > for modules which are not loaded. Only the first access will cause
> >> > the in-kernel module loader to pull-in the module. Systems which
> >> > never access the device node will not needlessly load the module,
> >> > and no longer need init scripts or other facilities to unconditionally
> >> > load it.
> >>
> >> Dmitry?
>
> > [dtor@hammer work]$ git describe --contains 8905aaafb4b5d9764c5b4b54c7d03eb41bb0a7e9
> > v2.6.36-rc3~19^2~2
>
> Awesome!
> So much for stupidly waiting-for-reply instead of just checking the reality. :)
>
Well, my fault really. Normally I try to let people know when I accept a
patch but I neglected doing this in this case...
--
Dmitry
prev parent reply other threads:[~2010-09-19 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 12:58 Kay Sievers
2010-09-17 9:53 ` Kay Sievers
2010-09-17 16:05 ` Dmitry Torokhov
2010-09-17 16:59 ` Kay Sievers
2010-09-19 23:27 ` 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=20100919232751.GB6565@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=kay.sievers@vrfy.org \
--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
all inboxes | Powered by JetHome®