From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933347Ab2JDN6i (ORCPT ); Thu, 4 Oct 2012 09:58:38 -0400 Received: from mail-pa0-f46.google.com ([209.85.220.46]:41989 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933102Ab2JDN6g (ORCPT ); Thu, 4 Oct 2012 09:58:36 -0400 Date: Thu, 4 Oct 2012 06:58:32 -0700 From: Greg KH To: Josh Boyer Cc: Linus Torvalds , Andy Walls , Al Viro , Mauro Carvalho Chehab , Ming Lei , Kay Sievers , Lennart Poettering , Linux Kernel Mailing List , Kay Sievers , Linux Media Mailing List , Michael Krufky , Ivan Kalvachev 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() Message-ID: <20121004135832.GB15525@kroah.com> References: <506C562E.5090909@redhat.com> <20121003170907.GA23473@ZenIV.linux.org.uk> <20121003195059.GA13541@kroah.com> <3560b86d-e2ad-484d-ab6e-2b9048894a12@email.android.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 04, 2012 at 09:39:41AM -0400, Josh Boyer wrote: > > That said, there's clearly enough variation here that I think that for > > now I won't take the step to disable the udev part. I'll do the patch > > to support "direct filesystem firmware loading" using the udev default > > paths, and that hopefully fixes the particular case people see with > > media modules. > > As you probably noticed, we had a tester in the RH bug report success > with the commit you included yesterday. > > Do you think this is something worth including in the stable kernels > after it gets some further testing during the merge window? Perhaps > not that specific commit as there seems to be some additional changes > needed for configurable paths, etc, but a backport of the fleshed out > changeset might be wanted. > > We have a new enough udev in Fedora 17 to hit this issue with 3.5 and > 3.6 when we rebase. I'm sure other distributions will be in similar > circumstances soon if they aren't already. Udev isn't going to be > fixed, so having something working in these cases would be great. Yes, I don't have a problem taking this into the stable kernel releases once it gets some testing and fleshed out. I'll be watching it to see how it goes. thanks, greg k-h