From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [meghadey-crypto:interrupt_message_store 6/6] drivers/iommu/intel_irq_remapping.c:1156:35: error: 'struct irq_alloc_info' has no member named 'dev'; did you mean 'desc'?
Date: Thu, 27 Feb 2020 11:39:07 +0800 [thread overview]
Message-ID: <202002271106.8NhzLIc2%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]
tree: https://github.com/meghadey/crypto interrupt_message_store
head: 265987e33d76d5b64f2542e0516fda3a6855a97d
commit: 265987e33d76d5b64f2542e0516fda3a6855a97d [6/6] ims-msi: Enable IMS interrupts
config: x86_64-rhel-7.6 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
git checkout 265987e33d76d5b64f2542e0516fda3a6855a97d
# 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/iommu/intel_irq_remapping.c: In function 'intel_get_irq_domain':
>> drivers/iommu/intel_irq_remapping.c:1156:35: error: 'struct irq_alloc_info' has no member named 'dev'; did you mean 'desc'?
iommu = map_gen_dev_to_ir(info->dev);
^~~
desc
vim +1156 drivers/iommu/intel_irq_remapping.c
1140
1141 static struct irq_domain *intel_get_irq_domain(struct irq_alloc_info *info)
1142 {
1143 struct intel_iommu *iommu;
1144
1145 if (!info)
1146 return NULL;
1147
1148 switch (info->type) {
1149 case X86_IRQ_ALLOC_TYPE_MSI:
1150 case X86_IRQ_ALLOC_TYPE_MSIX:
1151 iommu = map_dev_to_ir(info->msi_dev);
1152 if (iommu)
1153 return iommu->ir_msi_domain;
1154 break;
1155 case X86_IRQ_ALLOC_TYPE_IMS:
> 1156 iommu = map_gen_dev_to_ir(info->dev);
1157 if (iommu)
1158 return iommu->ir_ims_domain;
1159 break;
1160 default:
1161 break;
1162 }
1163
1164 return NULL;
1165 }
1166
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 48913 bytes --]
reply other threads:[~2020-02-27 3:39 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=202002271106.8NhzLIc2%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.