From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Xinhui Pan" <Xinhui.Pan@amd.com>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/radeon: Add build directory to include path
Date: Wed, 15 Jun 2022 10:35:35 +0200 [thread overview]
Message-ID: <c861e442-e09b-fe20-609c-05bdcb867663@mailbox.org> (raw)
In-Reply-To: <8beac4f5-f7e8-31ab-bbf3-36a917979bfc@mailbox.org>
On 2022-04-14 18:57, Michel Dänzer wrote:
> On 2022-04-14 17:04, Masahiro Yamada wrote:
>> On Thu, Apr 14, 2022 at 10:50 PM Michel Dänzer
>> <michel.daenzer@mailbox.org> wrote:
>>> On 2022-04-14 15:34, Alex Deucher wrote:
>>>> On Thu, Apr 14, 2022 at 4:44 AM Christian König
>>>> <ckoenig.leichtzumerken@gmail.com> wrote:
>>>>> Am 14.04.22 um 09:37 schrieb Michel Dänzer:
>>>>>>
>>>>>> make -C build-amd64 M=drivers/gpu/drm
>>
>>
>> Maybe
>>
>> make O=build-arm64 drivers/gpu/drm/
>>
>> is the way you were searching for.
>>
>> It builds only drivers/gpu/drm/
>> in the separate directory.
>
> Indeed, that works.
I've come to realize that this doesn't produce the actual *.ko modules though. Is there a trick for building the modules, but only under drivers/gpu/drm/ ?
--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer
next prev parent reply other threads:[~2022-06-15 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 16:14 [PATCH] drm/radeon: Add build directory to include path Michel Dänzer
2022-04-14 6:24 ` Christian König
2022-04-14 7:37 ` Michel Dänzer
2022-04-14 8:44 ` Christian König
2022-04-14 8:56 ` Michel Dänzer
2022-04-14 13:34 ` Alex Deucher
2022-04-14 13:49 ` Michel Dänzer
2022-04-14 15:04 ` Masahiro Yamada
2022-04-14 16:57 ` Michel Dänzer
2022-06-15 8:35 ` Michel Dänzer [this message]
2022-06-18 22:08 ` Masahiro Yamada
2022-06-19 16:22 ` Ernst Sjöstrand
2022-06-20 7:42 ` Michel Dänzer
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=c861e442-e09b-fe20-609c-05bdcb867663@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=masahiroy@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;
as well as URLs for NNTP newsgroup(s).