From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org
Cc: kernel@collabora.com,
Maciej Falkowski <maciej.falkowski@linux.intel.com>,
Oded Gabbay <ogabbay@kernel.org>
Subject: Re: [PATCH 1/3] accel/ivpu: pages_use_count is now a refcount_t
Date: Fri, 28 Mar 2025 08:41:24 +0100 [thread overview]
Message-ID: <44f879d4-a4ae-4abc-9017-22f525d458ec@linux.intel.com> (raw)
In-Reply-To: <87wmca4ps5.fsf@intel.com>
Hi,
On 3/27/2025 1:32 PM, Jani Nikula wrote:
> On Thu, 27 Mar 2025, Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com> wrote:
>> Hi,
>>
>> On 3/27/2025 12:37 PM, Dmitry Osipenko wrote:
>>> On 3/27/25 14:30, Jani Nikula wrote:
>>>> On Thu, 27 Mar 2025, Boris Brezillon <boris.brezillon@collabora.com> wrote:
>>>>> Commit 051b6646d36d ("drm/shmem-helper: Use refcount_t for
>>>>> pages_use_count") changed the type of
>>>>> drm_gem_shmem_object::pages_use_count but accel drivers were left
>>>>> behind.
>>>>>
>>>>> Fixes: 051b6646d36d ("drm/shmem-helper: Use refcount_t for pages_use_count")
>>>>> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
>>>>> Cc: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>>>>> Cc: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
>>>>> Cc: Maciej Falkowski <maciej.falkowski@linux.intel.com>
>>>>> Cc: Oded Gabbay <ogabbay@kernel.org>
>>>>> Cc: dri-devel@lists.freedesktop.org
>>>>
>>>> Just for build, on the series,
>>>>
>>>> Tested-by: Jani Nikula <jani.nikula@intel.com>
>>>>
>>>> Please merge.
>>>
>>> Applied to misc-next
>>
>> This was applied in less then an hour after posting for review without any testing (building is not testing).
>> I can't see how this is up to community standards.
>> I would prefer that patches for accel/ivpu were merged by ivpu maintainers.
>> At least give us time to review them.
>
> I regret rushing Boris/Dmitry to merge. Sorry about that.
>
> My only excuse is that the build was broken, and the changes were small
> and mechanical, similar to what was done elsewhere to change the
> interfaces.
I guess it OK as this doesn't happen too often and I would probably do the same :)
Regards,
Jacek
next prev parent reply other threads:[~2025-03-28 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 10:42 [PATCH 1/3] accel/ivpu: pages_use_count is now a refcount_t Boris Brezillon
2025-03-27 10:42 ` [PATCH 2/3] accel/ivpu: s/drm_gem_shmem_v[un]map/drm_gem_shmem_v[un]map_locked/ Boris Brezillon
2025-03-27 10:47 ` Dmitry Osipenko
2025-03-27 10:43 ` [PATCH 3/3] accel/amdxdna: s/drm_gem_v[un]map_unlocked/drm_gem_v[un]map/ Boris Brezillon
2025-03-27 10:48 ` Dmitry Osipenko
2025-03-27 10:47 ` [PATCH 1/3] accel/ivpu: pages_use_count is now a refcount_t Dmitry Osipenko
2025-03-27 11:30 ` Jani Nikula
2025-03-27 11:37 ` Dmitry Osipenko
2025-03-27 12:19 ` Jacek Lawrynowicz
2025-03-27 12:32 ` Jani Nikula
2025-03-28 7:41 ` Jacek Lawrynowicz [this message]
2025-03-27 13:20 ` Dmitry Osipenko
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=44f879d4-a4ae-4abc-9017-22f525d458ec@linux.intel.com \
--to=jacek.lawrynowicz@linux.intel.com \
--cc=boris.brezillon@collabora.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kernel@collabora.com \
--cc=maciej.falkowski@linux.intel.com \
--cc=ogabbay@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 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.