From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: Oded Gabbay <ogabbay@kernel.org>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] accel: Build sub-directories based on config options
Date: Mon, 13 Mar 2023 12:46:59 +0100 [thread overview]
Message-ID: <d83ef2b2-e762-8dfb-cc0d-46cffcac46ee@linux.intel.com> (raw)
In-Reply-To: <20230301165304.GA3963532@linux.intel.com>
Thanks. Applied to drm-misc-next and cherry-picked to drm-misc-fixes.
On 01.03.2023 17:53, Stanislaw Gruszka wrote:
> On Wed, Mar 01, 2023 at 09:31:10AM -0700, Jeffrey Hugo wrote:
>> On 3/1/2023 9:25 AM, Stanislaw Gruszka wrote:
>>> When accel drivers are disabled do not process into
>>> sub-directories and create built-in archives:
>>>
>>> AR drivers/accel/habanalabs/built-in.a
>>> AR drivers/accel/ivpu/built-in.a
>>>
>>> Signed-off-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
>>
>> Should there be a fixes tag? Feels like something that should be
>> back-ported.
>
> This tag could be added:
>
> Fixes: 35b137630f08 ("accel/ivpu: Introduce a new DRM driver for Intel VPU")
>
> but since then Makefile changed with habanalabs addition.
>
> I expect this will go to drm-misc-fixes and then to linux 6.3-rcX
> from there, so (stable) back-port will not be needed.
>
> Regards
> Stanislaw
prev parent reply other threads:[~2023-03-13 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 16:25 [PATCH] accel: Build sub-directories based on config options Stanislaw Gruszka
2023-03-01 16:31 ` Jeffrey Hugo
2023-03-01 16:53 ` Stanislaw Gruszka
2023-03-01 17:08 ` Jeffrey Hugo
2023-03-13 11:46 ` Jacek Lawrynowicz [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=d83ef2b2-e762-8dfb-cc0d-46cffcac46ee@linux.intel.com \
--to=jacek.lawrynowicz@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=stanislaw.gruszka@linux.intel.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.