mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Shannon Nelson <snelson@pensando.io>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/net/ethernet/pensando/ionic/ionic_main.c:230:2: error: implicit declaration of function 'dynamic_hex_dump'; did you mean 'seq_hex_dump'?
Date: Sun, 13 Oct 2019 01:21:08 +0800	[thread overview]
Message-ID: <201910130107.4LNxj69R%lkp@intel.com> (raw)

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

Hi Shannon,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   1c0cc5f1ae5ee5a6913704c0d75a6e99604ee30a
commit: 938962d552296a85551ddb1a9996526b330c4b72 ionic: Add adminq action
date:   5 weeks ago
config: x86_64-randconfig-a002-201941 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
        git checkout 938962d552296a85551ddb1a9996526b330c4b72
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/net/ethernet/pensando/ionic/ionic_main.c: In function 'ionic_adminq_cb':
>> drivers/net/ethernet/pensando/ionic/ionic_main.c:230:2: error: implicit declaration of function 'dynamic_hex_dump'; did you mean 'seq_hex_dump'? [-Werror=implicit-function-declaration]
     dynamic_hex_dump("comp ", DUMP_PREFIX_OFFSET, 16, 1,
     ^~~~~~~~~~~~~~~~
     seq_hex_dump
   cc1: some warnings being treated as errors

vim +230 drivers/net/ethernet/pensando/ionic/ionic_main.c

   212	
   213	static void ionic_adminq_cb(struct ionic_queue *q,
   214				    struct ionic_desc_info *desc_info,
   215				    struct ionic_cq_info *cq_info, void *cb_arg)
   216	{
   217		struct ionic_admin_ctx *ctx = cb_arg;
   218		struct ionic_admin_comp *comp;
   219		struct device *dev;
   220	
   221		if (!ctx)
   222			return;
   223	
   224		comp = cq_info->cq_desc;
   225		dev = &q->lif->netdev->dev;
   226	
   227		memcpy(&ctx->comp, comp, sizeof(*comp));
   228	
   229		dev_dbg(dev, "comp admin queue command:\n");
 > 230		dynamic_hex_dump("comp ", DUMP_PREFIX_OFFSET, 16, 1,
   231				 &ctx->comp, sizeof(ctx->comp), true);
   232	
   233		complete_all(&ctx->work);
   234	}
   235	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30782 bytes --]

                 reply	other threads:[~2019-10-12 17:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201910130107.4LNxj69R%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snelson@pensando.io \
    /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

all inboxes | Powered by JetHome®