From: "Marek Vašut" <marek.vasut@gmail.com>
To: dtor_core@ameritech.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iforce: fix -ENOMEM check
Date: Mon, 30 Jan 2006 14:47:52 +0100 [thread overview]
Message-ID: <200601301447.52382.marek.vasut@gmail.com> (raw)
In-Reply-To: <200601292226.51488.dtor_core@ameritech.net>
Dne pondělí 30 ledna 2006 04:26 jste napsal(a):
> OK, the patch below should get it going... Please let me know if it makes
> device appear.
Yeah, it works :-)
Thanks a lot. Maybe this fix should get somehow in kernel tree.
next prev parent reply other threads:[~2006-01-30 13:48 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
2006-01-29 11:09 ` Marek Vašut
2006-01-30 3:26 ` Dmitry Torokhov
2006-01-30 13:47 ` Marek Vašut [this message]
-- 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=200601301447.52382.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=dtor_core@ameritech.net \
--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;
as well as URLs for NNTP newsgroup(s).