linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: kernel test robot <lkp@intel.com>
Cc: Dario Binacchi <dariobin@libero.it>,
	linux-kernel@vger.kernel.org, kbuild-all@lists.01.org,
	clang-built-linux@googlegroups.com,
	Jakub Kicinski <kuba@kernel.org>,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
	Wolfgang Grandegger <wg@grandegger.com>,
	YueHaibing <yuehaibing@huawei.com>,
	Zhang Qilong <zhangqilong3@huawei.com>,
	linux-can@vger.kernel.org,
	Alexander Stein <alexander.stein@systec-electronic.com>,
	Federico Vaga <federico.vaga@gmail.com>
Subject: Re: [PATCH 5/6] can: c_can: prepare to up the message objects number
Date: Thu, 25 Feb 2021 10:25:50 +0100	[thread overview]
Message-ID: <20210225092550.7si56liuid4hih3a@pengutronix.de> (raw)
In-Reply-To: <202102251401.8hMQFKMw-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2761 bytes --]

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/master v5.11]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch]
> 
> url:    https://github.com/0day-ci/linux/commits/Dario-Binacchi/can-c_can-add-support-to-64-messages-objects/20210225-070042
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git testing
> config: x86_64-randconfig-a006-20210225 (attached as .config)
> compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project a921aaf789912d981cbb2036bdc91ad7289e1523)
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # install x86_64 cross compiling tool for clang build
>         # apt-get install binutils-x86-64-linux-gnu
>         # https://github.com/0day-ci/linux/commit/9bbfc6bc12c1d9a2445413bf6e710302f012c1ae
>         git remote add linux-review https://github.com/0day-ci/linux
>         git fetch --no-tags linux-review Dario-Binacchi/can-c_can-add-support-to-64-messages-objects/20210225-070042
>         git checkout 9bbfc6bc12c1d9a2445413bf6e710302f012c1ae
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
> >> drivers/net/can/c_can/c_can_pci.c:152:24: error: too few arguments to function call, single argument 'msg_obj_num' was not specified
>            dev = alloc_c_can_dev();
>                  ~~~~~~~~~~~~~~~ ^
>    drivers/net/can/c_can/c_can.h:212:20: note: 'alloc_c_can_dev' declared here
>    struct net_device *alloc_c_can_dev(int msg_obj_num);
>                       ^
>    1 error generated.

For now you can use 16, which means no change. I've added Alexander
and Federico to Cc, they added the intel pch and st micro support, maybe
they can help and add the correct size.

regards,
Marc

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-02-25  9:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 22:52 [PATCH 0/6] can: c_can: add support to 64 messages objects Dario Binacchi
2021-02-24 22:52 ` [PATCH 1/6] can: c_can: remove unused code Dario Binacchi
2021-02-24 22:52 ` [PATCH 2/6] can: c_can: fix indentation Dario Binacchi
2021-02-24 22:52 ` [PATCH 3/6] can: c_can: fix control interface used by c_can_do_tx Dario Binacchi
2021-02-24 22:52 ` [PATCH 4/6] can: c_can: use 32-bit write to set arbitration register Dario Binacchi
2021-02-24 22:52 ` [PATCH 5/6] can: c_can: prepare to up the message objects number Dario Binacchi
2021-02-25  7:14   ` kernel test robot
2021-02-25  9:25     ` Marc Kleine-Budde [this message]
2021-02-25  7:23   ` Marc Kleine-Budde
2021-02-24 22:52 ` [PATCH 6/6] can: c_can: add support to 64 messages objects Dario Binacchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210225092550.7si56liuid4hih3a@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=alexander.stein@systec-electronic.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=dariobin@libero.it \
    --cc=federico.vaga@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=socketcan@hartkopp.net \
    --cc=wg@grandegger.com \
    --cc=yuehaibing@huawei.com \
    --cc=zhangqilong3@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).