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]
Message-ID: <20140724115252.1847dbad@endymion.delvare>
Date:	Thu, 24 Jul 2014 11:52:52 +0200
From:	Jean Delvare <jdelvare@...e.de>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Dmitry Tarnyagin <dmitry.tarnyagin@...kless.no>,
	Ohad Ben-Cohen <ohad@...ery.com>
Subject: Re: Run-time dependencies for STE Modem remoteproc driver

Hi Linus,

On Wed, 23 Jul 2014 17:21:17 +0200, Linus Walleij wrote:
> On Mon, Jul 21, 2014 at 6:15 PM, Jean Delvare <jdelvare@...e.de> wrote:
> 
> > This brings the question: on which architectures / platforms is the STE
> > Modem remoteproc driver needed?
> 
> NONE.

Hm, OK :D So I will disable this driver in all our kernels. Maybe this
should be mentioned in the Kconfig help text?

Still, I suppose that the driver had an intended target, maybe we can
use that as a run-time dependency? Or should we just make the driver
depend on COMPILE_TEST?

Thanks,
-- 
Jean Delvare
SUSE L3 Support
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ