From: Matthew Wilcox <willy@infradead.org>
To: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch
Subject: Re: [PATCH v2 0/6] DRM IDR to Xarray conversions
Date: Fri, 22 Aug 2025 15:53:06 +0100 [thread overview]
Message-ID: <aKiEUlldVf2YazK9@casper.infradead.org> (raw)
In-Reply-To: <e80a3fd9-56ca-40c5-8ac8-237ce14cc79f@oracle.com>
On Fri, Aug 22, 2025 at 10:36:24AM -0400, Sidhartha Kumar wrote:
> On 8/22/25 8:33 AM, Jani Nikula wrote:
> > It would be great if the commit messages mentioned whether the
> > identifiers are expected to remain the same in the conversion.
>
> By identifiers do you mean if the name of the previous idr variable is the
> same as the XArray variable that is introduced? Sure I can add that in a v3.
I think Jani means that the actual numbers assigned should remain the
saame after the conversion.
next prev parent reply other threads:[~2025-08-22 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 14:54 [PATCH v2 0/6] DRM IDR to Xarray conversions Sidhartha Kumar
2025-08-21 14:54 ` [PATCH v2 1/6] drm: Convert aux_idr to XArray Sidhartha Kumar
2025-08-21 14:54 ` [PATCH v2 2/6] drm: Convert object_name_idr " Sidhartha Kumar
2025-08-21 14:54 ` [PATCH v2 3/6] drm: Convert syncobj_idr " Sidhartha Kumar
2025-08-21 14:54 ` [PATCH v2 4/6] drm: Convert magic_map " Sidhartha Kumar
2025-08-21 14:54 ` [PATCH v2 5/6] drm: Convert lessee_idr " Sidhartha Kumar
2025-08-21 14:54 ` [PATCH v2 6/6] drm: Convert tile_idr " Sidhartha Kumar
2025-08-22 12:33 ` [PATCH v2 0/6] DRM IDR to Xarray conversions Jani Nikula
2025-08-22 14:36 ` Sidhartha Kumar
2025-08-22 14:53 ` Matthew Wilcox [this message]
2025-08-25 6:52 ` Jani Nikula
2025-08-25 15:20 ` Sidhartha Kumar
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=aKiEUlldVf2YazK9@casper.infradead.org \
--to=willy@infradead.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sidhartha.kumar@oracle.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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).