linux-kernel - Re: [PATCH v3 01/11] stm class: Introduce an abstraction for System Trace Module devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Jul 2015 16:46:49 +0300
From:	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	Chunyan Zhang <zhang.lyra@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	Mathieu Poirier <mathieu.poirier@...aro.org>,
	peter.lachner@...el.com, norbert.schulz@...el.com,
	keven.boell@...el.com, yann.fouassier@...el.com,
	laurent.fert@...el.com,
	"linux-api\@vger.kernel.org" <linux-api@...r.kernel.org>,
	Chunyan Zhang <zhang.chunyan@...aro.org>
Subject: Re: [PATCH v3 01/11] stm class: Introduce an abstraction for System Trace Module devices

Mark Brown <broonie@...nel.org> writes:

> On Wed, Jul 29, 2015 at 04:25:10PM +0300, Alexander Shishkin wrote:
>
>> There has to be a way to defer stm_probe(), although a quick look at
>> amba code suggests it's not implemented.
>
> What makes you say this?  Probe deferral is implemented in the driver
> core rather than individual buses, the buses don't need to know anything
> about it.

I stand corrected, it indeed is.

So returning EPROBE_DEFER from stm_probe() should Just Work (provided
stm_probe() handles its error paths correctly).

Regards,
--
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/