From: kbuild test robot <lkp@intel.com>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: kbuild-all@01.org, iommu@lists.linux-foundation.org,
x86@kernel.org, linux-kernel@vger.kernel.org, joro@8bytes.org,
jroedel@suse.de,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH 3/3] iommu/amd: Add support for IOMMU XT mode
Date: Sat, 23 Jun 2018 12:01:04 +0800 [thread overview]
Message-ID: <201806231014.Os3JIL8Q%fengguang.wu@intel.com> (raw)
In-Reply-To: <1529686927-7665-4-git-send-email-suravee.suthikulpanit@amd.com>
Hi Suravee,
I love your patch! Perhaps something to improve:
[auto build test WARNING on iommu/next]
[also build test WARNING on v4.18-rc1 next-20180622]
[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/Suravee-Suthikulpanit/iommu-amd-Enable-x2APIC-support/20180623-032902
base: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-06-23 4:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 17:02 [PATCH 0/3] iommu/amd: Enable x2APIC support Suravee Suthikulpanit
2018-06-22 17:02 ` [PATCH 1/3] x86: irq_remapping: Move irq remapping mode enum Suravee Suthikulpanit
2018-06-22 17:02 ` [PATCH 2/3] iommu/amd: Add support for higher 64-bit IOMMU Control Register Suravee Suthikulpanit
2018-06-22 17:02 ` [PATCH 3/3] iommu/amd: Add support for IOMMU XT mode Suravee Suthikulpanit
2018-06-23 4:01 ` [RFC PATCH] iommu/amd: amd_iommu_xt_mode can be static kbuild test robot
2018-06-23 4:01 ` kbuild test robot [this message]
2018-06-27 9:29 ` [PATCH 0/3] iommu/amd: Enable x2APIC support Joerg Roedel
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=201806231014.Os3JIL8Q%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=x86@kernel.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 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®