From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev multithread
Date: Wed, 25 Feb 2009 22:11:50 +0000 [thread overview]
Message-ID: <49A5C226.3080607@tuffmail.co.uk> (raw)
In-Reply-To: <49A26771.5090709@tuffmail.co.uk>
Alan Jenkins wrote:
> alain T. wrote:
>> Hello,
>> sorry to disturb you, i read a lot about a multithread patch you made
>> for udev.
>> Is it alread merged in udev 138 ?
>> if not, can you please tell me where can i find it .
>
> It's not merged. Unfortunately I hit what seems to be a kernel bug
> and got stuck.
>
> The latest patch I posted was here:
> <http://marc.info/?l=linux-hotplug&m\x123040472620777&w=2>
> Hopefully it should be straightforward to apply.
>
> If you'd like to look at the kernel bug, I'll dig the details out for
> you. But I don't have a minimal test case, the steps to reproduce
> start with "install debian" :-).
Heh, actually the kernel is fine. It was my code that was buggy. I'll
try submitting it soon, without the bugs!
Alan
prev parent reply other threads:[~2009-02-25 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 9:08 udev multithread Alan Jenkins
2009-02-25 22:11 ` Alan Jenkins [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=49A5C226.3080607@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--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).