netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, peppe.cavallaro@st.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] stmmac: replace all pr_xxx by their netdev_xxx counterpart
Date: Thu, 5 Nov 2015 13:29:20 +0100	[thread overview]
Message-ID: <20151105122920.GB12736@Red> (raw)
In-Reply-To: <201511051818.nxWLifh7%fengguang.wu@intel.com>

On Thu, Nov 05, 2015 at 06:58:17PM +0800, kbuild test robot wrote:
> Hi LABBE,
> 
> [auto build test ERROR on: net/master]
> [also build test ERROR on: v4.3 next-20151105]
> 
> url:    https://github.com/0day-ci/linux/commits/LABBE-Corentin/stmmac-replace-all-pr_xxx-by-their-netdev_xxx-counterpart/20151105-163344
> config: m68k-allyesconfig (attached as .config)
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         make.cross ARCH=m68k 
> 
> Note: the linux-review/LABBE-Corentin/stmmac-replace-all-pr_xxx-by-their-netdev_xxx-counterpart/20151105-163344 HEAD 6d5b68276276235c73d865a816807f6073f341e9 builds fine.
>       It only hurts bisectibility.
> 
> All error/warnings (new ones prefixed by >>):
> 
>    drivers/net/ethernet/stmicro/stmmac/stmmac_main.c: In function 'stmmac_open':
> >> drivers/net/ethernet/stmicro/stmmac/stmmac_main.c:1822:7: error: expected ')' before '__func__'
>           __func__);
>           ^
> >> drivers/net/ethernet/stmicro/stmmac/stmmac_main.c:1822:7: warning: format '%s' expects a matching 'char *' argument [-Wformat=]
> 
> vim +1822 drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> 
>   1816		priv->dma_rx_size = STMMAC_ALIGN(dma_rxsize);
>   1817		priv->dma_buf_sz = STMMAC_ALIGN(buf_sz);
>   1818	
>   1819		ret = alloc_dma_desc_resources(priv);
>   1820		if (ret < 0) {
>   1821			netdev_err(priv->dev, "%s: DMA descriptors allocation failed\n"
> > 1822				   __func__);
>   1823			goto dma_desc_error;
>   1824		}
>   1825	
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

This part is removed by subsequent patch.
I will send a fixed version.

Regards

  reply	other threads:[~2015-11-05 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  8:30 [PATCH v3] stmmac: improve logging LABBE Corentin
2015-11-05  8:30 ` [PATCH v3 1/5] stmmac: replace all pr_xxx by their netdev_xxx counterpart LABBE Corentin
2015-11-05 10:58   ` kbuild test robot
2015-11-05 12:29     ` LABBE Corentin [this message]
2015-11-05  8:30 ` [PATCH v3 2/5] stmmac: replace hardcoded function name by __func__ LABBE Corentin
2015-11-05  8:30 ` [PATCH v3 3/5] stmmac: remove some __func__ printing LABBE Corentin
2015-11-05  8:30 ` [PATCH v3 4/5] stmmac: Fix simple style problem LABBE Corentin
2015-11-05  8:30 ` [PATCH v3 5/5] net: stmmac: replace if (netif_msg_type) by their netif_xxx counterpart LABBE Corentin

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=20151105122920.GB12736@Red \
    --to=clabbe.montjoie@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.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).