Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <bc37337ff82e187e39d029ee9f488d81e2b4fb44.camel@chromium.org>
Subject: Re: linux-next: Tree for Dec 7 (bpf: sock_from_file)
From:   Florent Revest <revest@chromium.org>
To:     Randy Dunlap <rdunlap@infradead.org>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Florent Revest <revest@google.com>, bpf <bpf@vger.kernel.org>
Date:   Mon, 07 Dec 2020 20:44:01 +0100
In-Reply-To: <b8f2e76b-a35e-55c5-e937-eea81700c994@infradead.org>
References: <20201207202520.3ced306c@canb.auug.org.au>
         <b8f2e76b-a35e-55c5-e937-eea81700c994@infradead.org>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.4-2 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Mon, 2020-12-07 at 10:39 -0800, Randy Dunlap wrote:
> On 12/7/20 1:25 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20201204:
> > 
> 
> on i386:
> # CONFIG_NET is not set
> 
> ld: kernel/trace/bpf_trace.o: in function `bpf_sock_from_file':
> bpf_trace.c:(.text+0xe23): undefined reference to `sock_from_file'
> 

Thanks Randy! I'm on it, I'll send a fix to bpf-next.