From: Kurt H Maier <khm@sdf.org>
To: linux-kernel@vger.kernel.org
Subject: Re: udev breakages - was: Re: Need of an ".async_probe()" type of callback at driver's core - Was: Re: [PATCH] [media] drxk: change it to use request_firmware_nowait()
Date: Thu, 4 Oct 2012 10:50:23 -0400 [thread overview]
Message-ID: <20121004145022.GA73321@intma.in> (raw)
In-Reply-To: <fa.lpiFTa5CtuIkUf2Z5eJ0YlsNwYI@ifi.uio.no>
On Wed, Oct 03, 2012 at 07:27:01PM +0000, Al Viro wrote:
>
> Al, that -><- close to volunteering for maintaining that FPOS kernel-side...
>
This would be fantastic.
Kurt H Maier
next parent reply other threads:[~2012-10-04 14:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.90I1W/wmSTgRFXVG67o7Pp3+rKA@ifi.uio.no>
[not found] ` <fa.Oszo+r/ZqdTxC2FHqqg+CRVMJ5Y@ifi.uio.no>
[not found] ` <fa.CoxzZZId9dJONv353c+pFG/HO8E@ifi.uio.no>
[not found] ` <fa.ixJ/7D7BnMK8xp7CwikX7jbmnKU@ifi.uio.no>
[not found] ` <fa./ubRQE7P/T+ateohnOKdDxOFhL4@ifi.uio.no>
[not found] ` <fa.lpiFTa5CtuIkUf2Z5eJ0YlsNwYI@ifi.uio.no>
2012-10-04 14:50 ` Kurt H Maier [this message]
2012-10-05 8:03 ` udev breakages - was: Re: Need of an ".async_probe()" type of callback at driver's core - Was: Re: [PATCH] [media] drxk: change it to use request_firmware_nowait() Emmanuel Benisty
2012-10-05 20:17 ` david
2012-10-05 21:43 ` Henrique de Moraes Holschuh
2012-10-06 19:09 ` udev breakages - Nix
[not found] <1340285798-8322-1-git-send-email-mchehab@redhat.com>
[not found] ` <4FE37194.30407@redhat.com>
[not found] ` <4FE8B8BC.3020702@iki.fi>
[not found] ` <4FE8C4C4.1050901@redhat.com>
[not found] ` <4FE8CED5.104@redhat.com>
[not found] ` <20120625223306.GA2764@kroah.com>
[not found] ` <4FE9169D.5020300@redhat.com>
2012-10-02 13:03 ` udev breakages - was: Re: Need of an ".async_probe()" type of callback at driver's core - Was: Re: [PATCH] [media] drxk: change it to use request_firmware_nowait() Mauro Carvalho Chehab
2012-10-02 16:33 ` Linus Torvalds
2012-10-02 21:03 ` Ivan Kalvachev
2012-10-02 22:37 ` Linus Torvalds
2012-10-03 22:15 ` Lucas De Marchi
2012-10-11 18:33 ` Shea Levy
2012-10-12 1:55 ` Ming Lei
2012-10-02 22:12 ` Greg KH
2012-10-02 22:23 ` Greg KH
2012-10-02 22:47 ` Linus Torvalds
2012-10-03 0:01 ` Jiri Kosina
2012-10-03 0:12 ` Linus Torvalds
2012-10-04 14:36 ` Jiri Kosina
2012-10-03 15:13 ` Mauro Carvalho Chehab
2012-10-03 16:38 ` Linus Torvalds
2012-10-03 17:00 ` Linus Torvalds
2012-10-03 17:09 ` Al Viro
2012-10-03 17:32 ` Linus Torvalds
2012-10-03 19:26 ` Al Viro
2012-10-03 19:50 ` Greg KH
2012-10-03 20:39 ` Linus Torvalds
2012-10-03 21:04 ` Kay Sievers
2012-10-03 21:05 ` Greg KH
2012-10-03 21:18 ` Kay Sievers
2012-10-03 21:45 ` Alan Cox
2012-10-03 21:58 ` Lucas De Marchi
2012-10-03 22:17 ` Linus Torvalds
2012-10-03 22:48 ` Andy Walls
2012-10-03 22:58 ` Linus Torvalds
2012-10-04 2:39 ` Kay Sievers
2012-10-04 13:39 ` Josh Boyer
2012-10-04 13:58 ` Greg KH
2012-10-03 22:53 ` Stephen Rothwell
2012-10-03 21:10 ` Andy Walls
[not found] ` <CACVXFVNTZmG+zTQNi9mCn9ynsCjkM084TmHKDcYYggtqLfhqNQ@mail.gmail.com>
2012-10-04 1:42 ` Linus Torvalds
2012-10-03 14:12 ` Mauro Carvalho Chehab
2012-10-03 14:36 ` Kay Sievers
2012-10-03 14:44 ` Linus Torvalds
2012-10-03 16:57 ` Greg KH
2012-10-03 17:24 ` Kay Sievers
2012-10-03 18:07 ` Linus Torvalds
2012-10-03 19:46 ` Mauro Carvalho Chehab
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=20121004145022.GA73321@intma.in \
--to=khm@sdf.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;
as well as URLs for NNTP newsgroup(s).