From: liweihang <liweihang@huawei.com>
To: "Xiong, Jianxin" <jianxin.xiong@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [rdma-core] Compile issue with DRM headers
Date: Mon, 22 Mar 2021 06:25:55 +0000 [thread overview]
Message-ID: <702e45fcf9e2470d8e46f9b69918188e@huawei.com> (raw)
In-Reply-To: MW3PR11MB45551494FA14979B4A0D8E50E5659@MW3PR11MB4555.namprd11.prod.outlook.com
On 2021/3/22 14:00, Xiong, Jianxin wrote:
>> -----Original Message-----
>> From: Jason Gunthorpe <jgg@ziepe.ca>
>> Sent: Sunday, March 21, 2021 8:53 AM
>> To: Leon Romanovsky <leon@kernel.org>
>> Cc: Xiong, Jianxin <jianxin.xiong@intel.com>; liweihang <liweihang@huawei.com>; linux-rdma@vger.kernel.org; Linuxarm
>> <linuxarm@huawei.com>
>> Subject: Re: [rdma-core] Compile issue with DRM headers
>>
>> On Sun, Mar 21, 2021 at 02:06:55PM +0200, Leon Romanovsky wrote:
>>> On Fri, Mar 19, 2021 at 04:50:53PM +0000, Xiong, Jianxin wrote:
> ....
>
>>>
>>> Let's add compilation test that checks all those files at the same time:
>>> 14 #include <drm.h>
>>> 15 #include <i915_drm.h>
>>> 16 #include <amdgpu_drm.h>
>>> 17 #include <radeon_drm.h>
>>
>> Yes please
>>
>> Jason
>
> I will work on this.
>
> Thanks,
>
> Jianxin
>
Thank you. I will help test on my server after your work is done :)
Weihang
prev parent reply other threads:[~2021-03-22 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 8:43 [rdma-core] Compile issue with DRM headers liweihang
2021-03-19 16:50 ` Xiong, Jianxin
2021-03-21 12:06 ` Leon Romanovsky
2021-03-21 15:53 ` Jason Gunthorpe
2021-03-22 6:00 ` Xiong, Jianxin
2021-03-22 6:25 ` liweihang [this message]
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=702e45fcf9e2470d8e46f9b69918188e@huawei.com \
--to=liweihang@huawei.com \
--cc=jgg@ziepe.ca \
--cc=jianxin.xiong@intel.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@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 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.