legacy: drop options that are now forcibly enabled
authorYann E. MORIN <yann.morin.1998@free.fr>
Mon, 24 Aug 2020 17:16:25 +0000 (19:16 +0200)
committerYann E. MORIN <yann.morin.1998@free.fr>
Mon, 24 Aug 2020 17:16:25 +0000 (19:16 +0200)
commit7292cbe80b92a01c9b66b6b9a2edbd194bd46edf
tree88f786e21dd8a342a212863b01a488aab49a8277
parent1861514be311beec600dd440a6afe2c2a367b031
legacy: drop options that are now forcibly enabled

As Thomas said:

> In this sort of situation, we generally don't add any legacy
> handling.  Indeed, since the feature is now mandatory... the
> default behavior will always be OK.

> People who could be annoyed are people who had this feature
> disabled... which is now always enabled. But the legacy handling
> will anyway not help those people.

Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Config.in.legacy