Re: [PATCH 5/6] can: c_can: prepare to up the message objects number

2021-02-25 Thread Marc Kleine-Budde
On 25.02.2021 15:14:43, kernel test robot wrote: > Hi Dario, > > Thank you for the patch! Yet something to improve: > > [auto build test ERROR on mkl-can-next/testing] > [also build test ERROR on linux/master net-next/master net/master > linus/master next-20210225] > [cannot apply to sparc-next/

Re: [PATCH 5/6] can: c_can: prepare to up the message objects number

2021-02-24 Thread Marc Kleine-Budde
Hey Dario, just a quick note... On 24.02.2021 23:52:45, Dario Binacchi wrote: > -struct net_device *alloc_c_can_dev(void) > +struct net_device *alloc_c_can_dev(int msg_obj_num) > { > struct net_device *dev; > struct c_can_priv *priv; > + int msg_obj_tx_num = msg_obj_num / 2; >

Re: [PATCH 5/6] can: c_can: prepare to up the message objects number

2021-02-24 Thread kernel test robot
Hi Dario, Thank you for the patch! Yet something to improve: [auto build test ERROR on mkl-can-next/testing] [also build test ERROR on linux/master net-next/master net/master linus/master next-20210225] [cannot apply to sparc-next/master v5.11] [If your patch is applied to the wrong git tree, ki

[PATCH 5/6] can: c_can: prepare to up the message objects number

2021-02-24 Thread Dario Binacchi
As pointed by commit c0a9f4d396c9 ("can: c_can: Reduce register access") the "driver casts the 16 message objects in stone, which is completely braindead as contemporary hardware has up to 128 message objects". The patch prepares the module to extend the number of message objects beyond the 32 cur