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-next>] [day] [month] [year] [list]
Message-ID: <d615e441-dcee-52a8-376b-f1b83eef0789@linaro.org>
Date:   Tue, 1 Sep 2020 15:22:31 -0500
From:   Alex Elder <elder@...aro.org>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Networking <netdev@...r.kernel.org>
Subject: COMPILE_TEST

Jakub, you suggested/requested that the Qualcomm IPA driver get
built when the COMPILE_TEST config option is enabled.  I started
working on this a few months ago but didn't finish, and picked
it up again today.  I'd really like to get this done soon.

The QCOM_IPA config option depends on and selects other things,
and those other things depend on and select still more config
options.  I've worked through some of these, but now question
whether this is even the right approach.  Should I try to ensure
all the code the IPA driver depends on and selects *also* gets
built when COMPILE_TEST is enabled?  Or should I try to minimize
the impact on other code by making IPA config dependencies and
selections also depend on the value of COMPILE_TEST?

Is there anything you know of that describes best practice for
enabling a config option when COMPILE_TEST is enabled?

Thanks.

					-Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ