On 04/26/2017 08:14 PM, Oliver Hartkopp wrote:
> The introduced namespace support moved the BCM variables for procfs into a
> per-net data structure. This leads to a build failure with disabled procfs:
> 
> 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'
> 
> http://marc.info/?l=linux-can&m=149321842526524&w=2
> 
> Reported-by: Randy Dunlap <rdun...@infradead.org>
> Signed-off-by: Oliver Hartkopp <socket...@hartkopp.net>

Applied to can-next.

Thanks,
Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to