From: Jani Nikula <jani.nikula@intel.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, "Huang Rui" <ray.huang@amd.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/ttm: let struct ttm_device_funcs be placed in rodata
Date: Wed, 17 May 2023 12:26:51 +0300 [thread overview]
Message-ID: <87fs7vgvfo.fsf@intel.com> (raw)
In-Reply-To: <CADnq5_NL-Ouh5-NRaoRknPDRTq2NDKWcHKxDEXfmkuqgWL54kw@mail.gmail.com>
On Tue, 16 May 2023, Alex Deucher <alexdeucher@gmail.com> wrote:
> On Tue, May 16, 2023 at 4:05 AM Jani Nikula <jani.nikula@intel.com> wrote:
>>
>> On Thu, 09 Mar 2023, Jani Nikula <jani.nikula@intel.com> wrote:
>> > On Thu, 09 Mar 2023, Christian König <christian.koenig@amd.com> wrote:
>> >> Am 09.03.23 um 13:37 schrieb Jani Nikula:
>> >>> Make the struct ttm_device_funcs pointers const so the data can be placed in rodata.
>> >>>
>> >>> Cc: Christian Koenig <christian.koenig@amd.com>
>> >>> Cc: Huang Rui <ray.huang@amd.com>
>> >>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> >>
>> >> Good idea, Reviewed-by: Christian König <christian.koenig@amd.com>
>> >
>> > Thanks!
>> >
>> >> Should I push it to drm-misc-next or do you need it on some other branch?
>> >
>> > Go ahead, I'm not urgently depending on it.
>>
>> Christian, I guess this fell between the cracks? Can I just push it to
>> drm-misc-next?
>
> Go ahead. Christian is out of the office this week.
Thanks, pushed to drm-misc-next.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, "Huang Rui" <ray.huang@amd.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ttm: let struct ttm_device_funcs be placed in rodata
Date: Wed, 17 May 2023 12:26:51 +0300 [thread overview]
Message-ID: <87fs7vgvfo.fsf@intel.com> (raw)
In-Reply-To: <CADnq5_NL-Ouh5-NRaoRknPDRTq2NDKWcHKxDEXfmkuqgWL54kw@mail.gmail.com>
On Tue, 16 May 2023, Alex Deucher <alexdeucher@gmail.com> wrote:
> On Tue, May 16, 2023 at 4:05 AM Jani Nikula <jani.nikula@intel.com> wrote:
>>
>> On Thu, 09 Mar 2023, Jani Nikula <jani.nikula@intel.com> wrote:
>> > On Thu, 09 Mar 2023, Christian König <christian.koenig@amd.com> wrote:
>> >> Am 09.03.23 um 13:37 schrieb Jani Nikula:
>> >>> Make the struct ttm_device_funcs pointers const so the data can be placed in rodata.
>> >>>
>> >>> Cc: Christian Koenig <christian.koenig@amd.com>
>> >>> Cc: Huang Rui <ray.huang@amd.com>
>> >>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> >>
>> >> Good idea, Reviewed-by: Christian König <christian.koenig@amd.com>
>> >
>> > Thanks!
>> >
>> >> Should I push it to drm-misc-next or do you need it on some other branch?
>> >
>> > Go ahead, I'm not urgently depending on it.
>>
>> Christian, I guess this fell between the cracks? Can I just push it to
>> drm-misc-next?
>
> Go ahead. Christian is out of the office this week.
Thanks, pushed to drm-misc-next.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-05-17 9:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 12:37 [Intel-gfx] [PATCH] drm/ttm: let struct ttm_device_funcs be placed in rodata Jani Nikula
2023-03-09 12:37 ` Jani Nikula
2023-03-09 12:45 ` [Intel-gfx] " Christian König
2023-03-09 12:45 ` Christian König
2023-03-09 12:49 ` [Intel-gfx] " Jani Nikula
2023-03-09 12:49 ` Jani Nikula
2023-05-16 8:05 ` [Intel-gfx] " Jani Nikula
2023-05-16 8:05 ` Jani Nikula
2023-05-16 16:11 ` [Intel-gfx] " Alex Deucher
2023-05-16 16:11 ` Alex Deucher
2023-05-17 9:26 ` Jani Nikula [this message]
2023-05-17 9:26 ` Jani Nikula
2023-03-09 12:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-03-09 13:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-03-11 2:42 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-16 16:08 ` [Intel-gfx] [PATCH] " Thomas Zimmermann
2023-05-16 16:08 ` Thomas Zimmermann
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=87fs7vgvfo.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=alexdeucher@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ray.huang@amd.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.