[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250925-lovely-azure-saluki-398ad9@penduick>
Date: Thu, 25 Sep 2025 14:50:31 +0200
From: Maxime Ripard <mripard@...nel.org>
To: Sumit Semwal <sumit.semwal@...aro.org>
Cc: Benjamin Gaignard <benjamin.gaignard@...labora.com>,
Brian Starkey <Brian.Starkey@....com>, John Stultz <jstultz@...gle.com>,
"T.J. Mercier" <tjmercier@...gle.com>, Jonathan Corbet <corbet@....net>, Andrew Davis <afd@...com>,
Jared Kangas <jkangas@...hat.com>, Mattijs Korpershoek <mkorpershoek@...nel.org>,
linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org, linaro-mm-sig@...ts.linaro.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Bagas Sanjaya <bagasdotme@...il.com>
Subject: Re: [PATCH v4] Documentation: dma-buf: heaps: Add naming guidelines
Hi Sumit,
On Wed, Sep 10, 2025 at 11:40:11AM +0530, Sumit Semwal wrote:
> Hello Maxime,
>
>
> On Mon, 28 Jul 2025 at 13:51, Maxime Ripard <mripard@...nel.org> wrote:
> >
> > We've discussed a number of times of how some heap names are bad, but
> > not really what makes a good heap name.
> >
> > Let's document what we expect the heap names to look like.
> Thank you for the patch. In principle, I'm ok to take this patch, with
> the obvious understanding that if there are future heap name
> requirements that can't be satisfied with these rules, we will discuss
> and adapt the rules accordingly.
>
> I hope this sounds reasonable to all.
>
> If I don't hear any objections, I'll merge this by this weekend.
As far as I know, it's still not merged?
Maxime
Download attachment "signature.asc" of type "application/pgp-signature" (274 bytes)
Powered by blists - more mailing lists