From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Marek Vašut" <marek.vasut@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iforce: fix -ENOMEM check
Date: Sat, 28 Jan 2006 23:14:20 -0500 [thread overview]
Message-ID: <200601282314.21222.dtor_core@ameritech.net> (raw)
In-Reply-To: <200601281903.28176.marek.vasut@gmail.com>
On Saturday 28 January 2006 13:03, Marek Vašut wrote:
> I have tried that patch, but nothing changed ...
> That error is still there and no new device in /dev/input appears
You do have updated udev, don't you? Could you pease post your dmesg
with the patch applied?
--
Dmitry
next prev parent reply other threads:[~2006-01-29 4:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 18:03 [PATCH] iforce: fix -ENOMEM check Marek Vašut
2006-01-29 4:14 ` Dmitry Torokhov [this message]
2006-01-29 11:09 ` Marek Vašut
2006-01-30 3:26 ` Dmitry Torokhov
2006-01-30 13:47 ` Marek Vašut
-- strict thread matches above, loose matches on Subject: below --
2006-01-22 11:50 Guillemot joystick not working since 2.6.14 Marek Vašut
2006-01-22 19:55 ` Alexey Dobriyan
2006-01-23 5:48 ` Dmitry Torokhov
2006-01-23 15:28 ` [PATCH] iforce: fix -ENOMEM check Alexey Dobriyan
2006-01-25 5:51 ` Dmitry Torokhov
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=200601282314.21222.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
/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.