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  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:   Sat, 22 Aug 2020 13:16:04 -0700 (PDT)
From:   David Miller <>
Subject: Re: [PATCH net-next v3 0/5] Move MDIO drivers into there own

From: Andrew Lunn <>
Date: Sat, 22 Aug 2020 21:51:44 +0200

> I just got a 0-day warning. I will send a fixup soon.

I also get this when I simply type make after your changes:

WARNING: unmet direct dependencies detected for PCS_XPCS
  Depends on [n]: NETDEVICES [=y] && PCS_DEVICE [=n]
  Selected by [m]:
  - STMMAC_ETH [=m] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=y] && HAS_IOMEM [=y] && HAS_DMA [=y]

And then it prompts me for:

PCS device drivers (PCS_DEVICE) [N/m/y/?] (NEW)

This is on a tree that had an allmodconfig config before your changes.

I really don't think users should get prompted for things like this just because
the source files were rearranged into different directories.

Why don't you submit a full v4 once you've resolved all of these items?


Powered by blists - more mailing lists