[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAF=yD-+SdynkS3zhE34ykMja_JsH1C61wT61c+fEHqFCMmsWXQ@mail.gmail.com>
Date: Sun, 16 Dec 2018 15:05:43 -0500
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: David Miller <davem@...emloft.net>
Cc: Paolo Abeni <pabeni@...hat.com>,
Network Development <netdev@...r.kernel.org>,
Eric Dumazet <eric.dumazet@...il.com>, pjt@...gle.com,
LKML <linux-kernel@...r.kernel.org>, ecree@...arflare.com,
dwmw2@...radead.org
Subject: Re: [PATCH net-next v3 0/4] net: mitigate retpoline overhead
On Sun, Dec 16, 2018 at 2:19 PM David Miller <davem@...emloft.net> wrote:
>
> From: Paolo Abeni <pabeni@...hat.com>
> Date: Sun, 16 Dec 2018 19:55:40 +0100
>
> > Again, I messed it! I'm really sorry to waste everybody's time.
> > I was unable to give proper coverage with different configs. I tested
> > vs.:
> >
> > CONFIG_IPV6=ymn
> > CONFIG_INET=yn
> >
> > but
> >
> > # CONFIG_RETPOLINE is not set
> >
> > fooled me. The following patch should fix.
>
> Please submit this formally with a proper signoff and let's see where
> it goes.
I just happened to run in to this, too. Had to disable retpoline for
some unrelated issue.
The above draft patch fixed the compilation for me.
Powered by blists - more mailing lists