From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754305Ab3A3KxR (ORCPT ); Wed, 30 Jan 2013 05:53:17 -0500 Received: from cantor2.suse.de ([195.135.220.15]:42462 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753250Ab3A3KxP (ORCPT ); Wed, 30 Jan 2013 05:53:15 -0500 Date: Wed, 30 Jan 2013 11:53:14 +0100 Message-ID: From: Takashi Iwai To: Ming Lei Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/4] firmware: Refactoring for splitting user-mode helper code In-Reply-To: References: <1359470814-7993-1-git-send-email-tiwai@suse.de> <1359470814-7993-2-git-send-email-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.2 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Wed, 30 Jan 2013 18:50:05 +0800, Ming Lei wrote: > > On Wed, Jan 30, 2013 at 6:31 PM, Takashi Iwai wrote: > > > > But it's supposed to be cached, no? > > Generally it will be cached, but some crazy devices might come as new > device during resume, so we still need to handle the situation. In that case, shouldn't we simply return an error instead of usermodehelper lock (at least for direct loading)? Takashi