linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Shukun Tan <tanshukun1@huawei.com>
Cc: kbuild-all@lists.01.org, herbert@gondor.apana.org.au,
	davem@davemloft.net, linux-crypto@vger.kernel.org,
	xuzaibo@huawei.com, wangzhou1@hisilicon.com,
	jonathan.cameron@huawei.com
Subject: Re: [PATCH 1/4] crypto: hisilicon/qm - Put device finding logic into QM
Date: Thu, 5 Mar 2020 03:59:10 +0800	[thread overview]
Message-ID: <202003050327.uc4CfwH4%lkp@intel.com> (raw)
In-Reply-To: <1583308165-16800-2-git-send-email-tanshukun1@huawei.com>

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

Hi Shukun,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on cryptodev/master]
[also build test ERROR on next-20200304]
[cannot apply to crypto/master v5.6-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Shukun-Tan/crypto-hisilicon-Refactor-find-device-related-code/20200305-013355
base:   https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
config: riscv-allyesconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=riscv 

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

All errors (new ones prefixed by >>):

   drivers/crypto/hisilicon/qm.c: In function 'hisi_qm_sort_devices':
>> drivers/crypto/hisilicon/qm.c:2230:20: error: 'struct device' has no member named 'numa_node'; did you mean 'of_node'?
       dev_node = dev->numa_node;
                       ^~~~~~~~~
                       of_node

vim +2230 drivers/crypto/hisilicon/qm.c

  2216	
  2217	static int hisi_qm_sort_devices(int node, struct list_head *head,
  2218					struct hisi_qm_list *qm_list)
  2219	{
  2220		struct hisi_qm_resource *res, *tmp;
  2221		struct hisi_qm *qm;
  2222		struct list_head *n;
  2223		struct device *dev;
  2224		int dev_node = 0;
  2225	
  2226		list_for_each_entry(qm, &qm_list->list, list) {
  2227			dev = &qm->pdev->dev;
  2228	
  2229			if (IS_ENABLED(CONFIG_NUMA)) {
> 2230				dev_node = dev->numa_node;
  2231				if (dev_node < 0)
  2232					dev_node = 0;
  2233			}
  2234	
  2235			res = kzalloc(sizeof(*res), GFP_KERNEL);
  2236			if (!res)
  2237				return -ENOMEM;
  2238	
  2239			res->qm = qm;
  2240			res->distance = node_distance(dev_node, node);
  2241			n = head;
  2242			list_for_each_entry(tmp, head, list) {
  2243				if (res->distance < tmp->distance) {
  2244					n = &tmp->list;
  2245					break;
  2246				}
  2247			}
  2248			list_add_tail(&res->list, n);
  2249		}
  2250	
  2251		return 0;
  2252	}
  2253	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

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

  reply	other threads:[~2020-03-04 20:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  7:49 [PATCH 0/4] crypto: hisilicon - Refactor find device related code Shukun Tan
2020-03-04  7:49 ` [PATCH 1/4] crypto: hisilicon/qm - Put device finding logic into QM Shukun Tan
2020-03-04 19:59   ` kbuild test robot [this message]
2020-03-04  7:49 ` [PATCH 2/4] crypto: hisilicon/zip - Use hisi_qm_alloc_qps_node() when init ctx Shukun Tan
2020-03-04  7:49 ` [PATCH 3/4] crypto: hisilicon/hpre - Optimize finding hpre device process Shukun Tan
2020-03-04  7:49 ` [PATCH 4/4] crypto: hisilicon/sec2 - Add new create qp process Shukun Tan

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=202003050327.uc4CfwH4%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jonathan.cameron@huawei.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=tanshukun1@huawei.com \
    --cc=wangzhou1@hisilicon.com \
    --cc=xuzaibo@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).