All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: Good news for threading!
Date: Tue, 26 May 2009 09:36:44 +0000	[thread overview]
Message-ID: <4A1BB82C.7010308@tuffmail.co.uk> (raw)
In-Reply-To: <4A1AA131.7000202@tuffmail.co.uk>

Scott James Remnant wrote:
> On Mon, 2009-05-25 at 14:46 +0100, Alan Jenkins wrote:
>
>   
>> I solved one of the reservations that held me back on threaded udevd.  I 
>> still have some other concerns to work on, but I'm feeling much more 
>> optimistic now.
>>
>>     
> Are you maintaining a GIT tree of your threading work?  I'd be very
> interested in playing <g>
>
> Scott
>   

No, sorry.  I'm going to try to submit it all as patches Right Now.  I
will need to rewrite the madvise hack before I can submit that though.

Alan

      parent reply	other threads:[~2009-05-26  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 13:46 Good news for threading! Alan Jenkins
2009-05-25 19:09 ` Kay Sievers
2009-05-25 20:28 ` Alan Jenkins
2009-05-25 23:52 ` Kay Sievers
2009-05-26  7:03 ` Scott James Remnant
2009-05-26  9:32 ` Alan Jenkins
2009-05-26  9:36 ` 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=4A1BB82C.7010308@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 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.