From: lkp@intel.com (kbuild test robot)
Subject: [PATCH 1/4] nvme: factor out pci abort handling into core
Date: Fri, 20 Jul 2018 00:29:18 +0800 [thread overview]
Message-ID: <201807192335.ptGDRSvD%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180719132838.15556-2-jthumshirn@suse.de>
Hi Johannes,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18-rc5 next-20180719]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Johannes-Thumshirn/Rework-NVMe-abort-handling/20180719-230642
config: x86_64-randconfig-x011-201828 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/nvme/host/core.c: In function 'abort_endio':
>> drivers/nvme/host/core.c:711:40: error: 'struct nvme_request' has no member named 'ctrl'
struct nvme_ctrl *ctrl = nvme_req(req)->ctrl;
^~
vim +711 drivers/nvme/host/core.c
707
708
709 static void abort_endio(struct request *req, blk_status_t error)
710 {
> 711 struct nvme_ctrl *ctrl = nvme_req(req)->ctrl;
712
713 dev_warn(ctrl->device,
714 "Abort status: 0x%x", nvme_req(req)->status);
715 atomic_inc(&ctrl->abort_limit);
716 blk_mq_free_request(req);
717 }
718
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 34695 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20180720/d222223b/attachment-0001.gz>
next prev parent reply other threads:[~2018-07-19 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 13:28 [PATCH 0/4] Rework NVMe abort handling Johannes Thumshirn
2018-07-19 13:28 ` [PATCH 1/4] nvme: factor out pci abort handling into core Johannes Thumshirn
2018-07-19 16:29 ` kbuild test robot [this message]
2018-07-19 13:28 ` [PATCH 2/4] nvme: rdma: abort commands before resetting controller Johannes Thumshirn
2018-07-19 13:28 ` [PATCH 3/4] nvmet: loop: " Johannes Thumshirn
2018-07-19 13:28 ` [PATCH 4/4] nvme: fc: " Johannes Thumshirn
2018-07-19 13:42 ` [PATCH 0/4] Rework NVMe abort handling Christoph Hellwig
2018-07-19 14:10 ` Johannes Thumshirn
2018-07-19 14:23 ` Christoph Hellwig
2018-07-19 14:35 ` Johannes Thumshirn
2018-07-19 14:50 ` Christoph Hellwig
2018-07-19 14:54 ` Johannes Thumshirn
2018-07-19 15:04 ` James Smart
2018-07-20 6:36 ` Johannes Thumshirn
2018-07-19 15:00 ` James Smart
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=201807192335.ptGDRSvD%fengguang.wu@intel.com \
--to=lkp@intel.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