From: Takashi Iwai Subject: Re: [PATCH] ASoC: soc-core: remove error due to probe deferral Date: Thu, 08 Aug 2019 15:14:03 +0200 Message-ID: References: <20190808123655.31520-1-stefan@agner.ch> <20190808124437.GD3795@sirena.co.uk> <20190808130217.GE3795@sirena.co.uk> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20190808130217.GE3795@sirena.co.uk> Sender: linux-kernel-owner@vger.kernel.org To: Mark Brown Cc: Stefan Agner , alsa-devel@alsa-project.org, lgirdwood@gmail.com, perex@perex.cz, Stefan Agner , linux-kernel@vger.kernel.org List-Id: alsa-devel@alsa-project.org On Thu, 08 Aug 2019 15:02:17 +0200, Mark Brown wrote: > > On Thu, Aug 08, 2019 at 03:00:06PM +0200, Takashi Iwai wrote: > > Mark Brown wrote: > > > > No, they absolutely should tell the user why they are deferring so the > > > user has some information to go on when they're trying to figure out why > > > their device isn't instantiating. > > > But it's no real error that *must* be printed on the console, either. > > Maybe downgrading the printk level? > > Yes, downgrading can be OK though it does bloat the code. I guess we can use dev_printk() with the conditional level choice. Takashi