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:   Tue, 3 Aug 2021 09:14:34 -0700
From:   Richard Cochran <>
To:     Arnd Bergmann <>
Cc:     Nicolas Pitre <>,
        "Keller, Jacob E" <>,
        "Brandeburg, Jesse" <>,
        "Nguyen, Anthony L" <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        Arnd Bergmann <>,
        Kurt Kanzenbach <>,
        "Saleem, Shiraz" <>,
        "Ertman, David M" <>,
        "" <>,
        "" <>,
        "" <>
Subject: Re: [PATCH net-next v2] ethernet/intel: fix PTP_1588_CLOCK

On Tue, Aug 03, 2021 at 08:55:56AM -0700, Richard Cochran wrote:
> On Tue, Aug 03, 2021 at 08:59:02AM +0200, Arnd Bergmann wrote:
> > It may well be a lost cause, but a build fix is not the time to nail down
> > that decision. The fix I proposed (with the added MAY_USE_PTP_1588_CLOCK
> > symbol) is only two extra lines and leaves everything else working for the
> > moment.
> Well, then we'll have TWO ugly and incomprehensible Kconfig hacks,
> imply and MAY_USE.
> Can't we fix this once and for all?
> Seriously, "imply" has been nothing but a major PITA since day one,
> and all to save 22 kb.  I can't think of another subsystem which
> tolerates so much pain for so little gain.

Here is what I want to have, in accordance with the KISS principle:

config PTP_1588_CLOCK
	bool "PTP clock support"
	select NET
	select PPS

# driver variant 1:

config ACME_MAC
	select PTP_1588_CLOCK

# driver variant 2:

config ACME_MAC

	depends on ACME_MAC
	select PTP_1588_CLOCK



Powered by blists - more mailing lists