On Fri, 06 Jun 2025, Maxime Ripard wrote:
> Thanks for working on that. Your two patches (the one you sent here, and
> the one in the other subthread) look good to me. So if that works, it
> looks like we have a way forward.
Coincidentally, I just posted the first non-draft patches [1]. Thanks
fo
On Tue, May 27, 2025 at 10:40:49PM +0300, Jani Nikula wrote:
> On Tue, 27 May 2025, Maxime Ripard wrote:
> > On Tue, May 20, 2025 at 01:09:47PM +0300, Jani Nikula wrote:
> >>
> >> Maxime -
> >>
> >> I'm cutting a lot of context here. Not because I don't think it deserves
> >> an answer, but beca
On Tue, 27 May 2025, Maxime Ripard wrote:
> On Tue, May 20, 2025 at 01:09:47PM +0300, Jani Nikula wrote:
>>
>> Maxime -
>>
>> I'm cutting a lot of context here. Not because I don't think it deserves
>> an answer, but because I seem to be failing at communication.
>>
>> On Mon, 19 May 2025, Maxi
On Tue, 27 May 2025, Maxime Ripard wrote:
> Hi,
>
> On Fri, May 23, 2025 at 02:34:05PM +0300, Jani Nikula wrote:
>> On Tue, 20 May 2025, Jani Nikula wrote:
>> > Maxime -
>> >
>> > I'm cutting a lot of context here. Not because I don't think it deserves
>> > an answer, but because I seem to be fai
Hi,
On Fri, May 23, 2025 at 02:34:05PM +0300, Jani Nikula wrote:
> On Tue, 20 May 2025, Jani Nikula wrote:
> > Maxime -
> >
> > I'm cutting a lot of context here. Not because I don't think it deserves
> > an answer, but because I seem to be failing at communication.
> >
> > On Mon, 19 May 2025, M
On Tue, May 20, 2025 at 01:09:47PM +0300, Jani Nikula wrote:
>
> Maxime -
>
> I'm cutting a lot of context here. Not because I don't think it deserves
> an answer, but because I seem to be failing at communication.
>
> On Mon, 19 May 2025, Maxime Ripard wrote:
> > You still haven't explained wh
On Tue, 20 May 2025, Jani Nikula wrote:
> Maxime -
>
> I'm cutting a lot of context here. Not because I don't think it deserves
> an answer, but because I seem to be failing at communication.
>
> On Mon, 19 May 2025, Maxime Ripard wrote:
>> You still haven't explained why it would take anything m
Maxime -
I'm cutting a lot of context here. Not because I don't think it deserves
an answer, but because I seem to be failing at communication.
On Mon, 19 May 2025, Maxime Ripard wrote:
> You still haven't explained why it would take anything more than
> registering a dumb device at probe time
On Wed, May 14, 2025 at 12:22:40PM +0300, Jani Nikula wrote:
> On Tue, 13 May 2025, Maxime Ripard wrote:
> > Is it really surprising you get some pushback when you are using a
> > design that is the complete opposite to what every user of it for the
> > last decade has been doing?
>
> The opposit
On Fri, 16 May 2025, Anusha Srivatsa wrote:
> On Wed, May 14, 2025 at 5:22 AM Jani Nikula
> wrote:
>
>> On Tue, 13 May 2025, Maxime Ripard wrote:
>> > Is it really surprising you get some pushback when you are using a
>> > design that is the complete opposite to what every user of it for the
>>
On Wed, May 14, 2025 at 5:22 AM Jani Nikula
wrote:
> On Tue, 13 May 2025, Maxime Ripard wrote:
> > Is it really surprising you get some pushback when you are using a
> > design that is the complete opposite to what every user of it for the
> > last decade has been doing?
>
> The opposite is also
On Tue, 13 May 2025, Maxime Ripard wrote:
> Is it really surprising you get some pushback when you are using a
> design that is the complete opposite to what every user of it for the
> last decade has been doing?
The opposite is also true.
If you create a design that does not cleanly fit the mod
On Fri, May 09, 2025 at 03:45:36PM +0300, Jani Nikula wrote:
> On Fri, 09 May 2025, Maxime Ripard wrote:
> > On Thu, May 08, 2025 at 05:27:21PM +0300, Jani Nikula wrote:
> >> On Mon, 05 May 2025, Anusha Srivatsa wrote:
> >> > On Mon, May 5, 2025 at 2:54 AM Maxime Ripard wrote:
> >> >
> >> >> Hi
On Mon, 12 May 2025, Anusha Srivatsa wrote:
> I get that embedding drm_panel within intel_panel which is embedded
> within intel_connector, which also embeds drm_connector and so on can
> get confusing to use. But Jani,
> about drm_panel_follower , which is the panel that is following the
> intel_
On Fri, May 9, 2025 at 8:45 AM Jani Nikula
wrote:
> On Fri, 09 May 2025, Maxime Ripard wrote:
> > On Thu, May 08, 2025 at 05:27:21PM +0300, Jani Nikula wrote:
> >> On Mon, 05 May 2025, Anusha Srivatsa wrote:
> >> > On Mon, May 5, 2025 at 2:54 AM Maxime Ripard
> wrote:
> >> >
> >> >> Hi Jani,
>
On Thu, 08 May 2025, Anusha Srivatsa wrote:
> On Thu, May 8, 2025 at 10:27 AM Jani Nikula
> wrote:
>
>> On Mon, 05 May 2025, Anusha Srivatsa wrote:
>> > On Mon, May 5, 2025 at 2:54 AM Maxime Ripard wrote:
>> >
>> >> Hi Jani,
>> >>
>> >> On Tue, Apr 29, 2025 at 12:22:00PM +0300, Jani Nikula wrot
On Fri, 09 May 2025, Maxime Ripard wrote:
> On Thu, May 08, 2025 at 05:27:21PM +0300, Jani Nikula wrote:
>> On Mon, 05 May 2025, Anusha Srivatsa wrote:
>> > On Mon, May 5, 2025 at 2:54 AM Maxime Ripard wrote:
>> >
>> >> Hi Jani,
>> >>
>> >> On Tue, Apr 29, 2025 at 12:22:00PM +0300, Jani Nikula w
On Thu, May 08, 2025 at 05:27:21PM +0300, Jani Nikula wrote:
> On Mon, 05 May 2025, Anusha Srivatsa wrote:
> > On Mon, May 5, 2025 at 2:54 AM Maxime Ripard wrote:
> >
> >> Hi Jani,
> >>
> >> On Tue, Apr 29, 2025 at 12:22:00PM +0300, Jani Nikula wrote:
> >> > On Tue, 29 Apr 2025, Maxime Ripard wr
On Thu, May 8, 2025 at 10:27 AM Jani Nikula
wrote:
> On Mon, 05 May 2025, Anusha Srivatsa wrote:
> > On Mon, May 5, 2025 at 2:54 AM Maxime Ripard wrote:
> >
> >> Hi Jani,
> >>
> >> On Tue, Apr 29, 2025 at 12:22:00PM +0300, Jani Nikula wrote:
> >> > On Tue, 29 Apr 2025, Maxime Ripard wrote:
> >
On Mon, 05 May 2025, Anusha Srivatsa wrote:
> On Mon, May 5, 2025 at 2:54 AM Maxime Ripard wrote:
>
>> Hi Jani,
>>
>> On Tue, Apr 29, 2025 at 12:22:00PM +0300, Jani Nikula wrote:
>> > On Tue, 29 Apr 2025, Maxime Ripard wrote:
>> > > Hi Jani,
>> > >
>> > > On Mon, Apr 28, 2025 at 07:31:50PM +0300
On Mon, May 5, 2025 at 2:54 AM Maxime Ripard wrote:
> Hi Jani,
>
> On Tue, Apr 29, 2025 at 12:22:00PM +0300, Jani Nikula wrote:
> > On Tue, 29 Apr 2025, Maxime Ripard wrote:
> > > Hi Jani,
> > >
> > > On Mon, Apr 28, 2025 at 07:31:50PM +0300, Jani Nikula wrote:
> > >> On Mon, 31 Mar 2025, Anusha
Hi Jani,
On Tue, Apr 29, 2025 at 12:22:00PM +0300, Jani Nikula wrote:
> On Tue, 29 Apr 2025, Maxime Ripard wrote:
> > Hi Jani,
> >
> > On Mon, Apr 28, 2025 at 07:31:50PM +0300, Jani Nikula wrote:
> >> On Mon, 31 Mar 2025, Anusha Srivatsa wrote:
> >> > Allocate panel via reference counting. Add _
On Tue, 29 Apr 2025, Maxime Ripard wrote:
> Hi Jani,
>
> On Mon, Apr 28, 2025 at 07:31:50PM +0300, Jani Nikula wrote:
>> On Mon, 31 Mar 2025, Anusha Srivatsa wrote:
>> > Allocate panel via reference counting. Add _get() and _put() helper
>> > functions to ensure panel allocations are refcounted.
Hi Jani,
On Mon, Apr 28, 2025 at 07:31:50PM +0300, Jani Nikula wrote:
> On Mon, 31 Mar 2025, Anusha Srivatsa wrote:
> > Allocate panel via reference counting. Add _get() and _put() helper
> > functions to ensure panel allocations are refcounted. Avoid use after
> > free by ensuring panel pointer
On Mon, 31 Mar 2025, Anusha Srivatsa wrote:
> Allocate panel via reference counting. Add _get() and _put() helper
> functions to ensure panel allocations are refcounted. Avoid use after
> free by ensuring panel pointer is valid and can be usable till the last
> reference is put.
>
> Reviewed-by: L
Allocate panel via reference counting. Add _get() and _put() helper
functions to ensure panel allocations are refcounted. Avoid use after
free by ensuring panel pointer is valid and can be usable till the last
reference is put.
Reviewed-by: Luca Ceresoli
Reviewed-by: Maxime Ripard
Signed-off-by:
26 matches
Mail list logo
