From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933171AbdDZSWL (ORCPT ); Wed, 26 Apr 2017 14:22:11 -0400 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.220]:27465 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933126AbdDZSWB (ORCPT ); Wed, 26 Apr 2017 14:22:01 -0400 X-RZG-AUTH: :P2MHfkW8eP4Mre39l357AZT/I7AY/7nT2yrT1q0ngWNsKR9DbcDvsfbZ70J0gs4NEuAwSg== X-RZG-CLASS-ID: mo00 Subject: Re: linux-next: Tree for Apr 26 (net/can/bcm.c) To: Randy Dunlap , Stephen Rothwell , Linux-Next Mailing List References: <20170426180321.3c8c16a2@canb.auug.org.au> <05bd24d8-6840-3551-a529-c464f3b26d0a@infradead.org> Cc: Linux Kernel Mailing List , "netdev@vger.kernel.org" , linux-can@vger.kernel.org From: Oliver Hartkopp Message-ID: <9e4a2928-73b7-8ab0-c851-79fcb27569f4@hartkopp.net> Date: Wed, 26 Apr 2017 20:18:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <05bd24d8-6840-3551-a529-c464f3b26d0a@infradead.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Randy, thanks for the report! Some fallout of my namespace support integration %-) I posted a patch for it: http://marc.info/?l=linux-can&m=149323049630039&w=2 Many thanks & best regards, Oliver On 04/26/2017 04:53 PM, Randy Dunlap wrote: > On 04/26/17 01:03, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20170424: >> > > on x86_64: > > when CONFIG_PROC_FS is not enabled: > > ../net/can/bcm.c:1541:14: error: 'struct netns_can' has no member named 'bcmproc_dir' > ../net/can/bcm.c:1601:14: error: 'struct netns_can' has no member named 'bcmproc_dir' > ../net/can/bcm.c:1696:11: error: 'struct netns_can' has no member named 'bcmproc_dir' > ../net/can/bcm.c:1707:15: error: 'struct netns_can' has no member named 'bcmproc_dir' > > 2 of those are "protected" by > if (IS_ENABLED(CONFIG_PROC_FS)) { > but that doesn't seem to help/work here. > > gcc v4.8.5 > > >