Thu, Feb 28, 2019 at 05:02:56PM CET, jakub.kicin...@netronome.com wrote:
>On Thu, 28 Feb 2019 16:01:25 +0100, Jiri Pirko wrote:
>> Tue, Feb 26, 2019 at 04:34:02AM CET, jakub.kicin...@netronome.com wrote:
>> >diff --git a/net/Kconfig b/net/Kconfig
>> >index 62da6148e9f8..1efe1f9ee492 100644
>> >---
On Thu, 28 Feb 2019 16:01:25 +0100, Jiri Pirko wrote:
> Tue, Feb 26, 2019 at 04:34:02AM CET, jakub.kicin...@netronome.com wrote:
> >diff --git a/net/Kconfig b/net/Kconfig
> >index 62da6148e9f8..1efe1f9ee492 100644
> >--- a/net/Kconfig
> >+++ b/net/Kconfig
> >@@ -429,21 +429,12 @@ config NET_SOCK_MS
Tue, Feb 26, 2019 at 04:34:02AM CET, jakub.kicin...@netronome.com wrote:
[...]
>diff --git a/net/Kconfig b/net/Kconfig
>index 62da6148e9f8..1efe1f9ee492 100644
>--- a/net/Kconfig
>+++ b/net/Kconfig
>@@ -429,21 +429,12 @@ config NET_SOCK_MSG
> with the help of BPF programs.
>
> config NE
Being able to build devlink as a module causes growing pains.
First all drivers had to add a meta dependency to make sure
they are not built in when devlink is built as a module. Now
we are struggling to invoke ethtool compat code reliably.
Make devlink code built-in, users can still not build it