[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DBPTT2WUK2CH.1V1KX11EJPIFB@brighamcampbell.com>
Date: Wed, 30 Jul 2025 18:49:42 -0600
From: "Brigham Campbell" <me@...ghamcampbell.com>
To: "Doug Anderson" <dianders@...omium.org>
Cc: <maarten.lankhorst@...ux.intel.com>, <mripard@...nel.org>,
<tzimmermann@...e.de>, <airlied@...il.com>, <simona@...ll.ch>,
<linus.walleij@...aro.org>, <neil.armstrong@...aro.org>,
<jessica.zhang@....qualcomm.com>, <sam@...nborg.org>,
<skhan@...uxfoundation.org>, <linux-kernel-mentees@...ts.linux.dev>,
<dri-devel@...ts.freedesktop.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/3] drm: Add MIPI read_multi func and two write
macros
On Wed Jul 30, 2025 at 9:56 AM MDT, Doug Anderson wrote:
>> +/**
>> + * mipi_dsi_dcs_write_var_seq_multi - transmit a DCS command with non-static
>> + * payload
>
> I should have been explicit, but the above "non-static" should also be
> "non-constant". ;-)
>
> I could probably fix that when applying, or you could send a v4. Up to you.
Oops. This obviously needed to change as well, but I tunnel-visioned
hard. I'll go ahead and fix it in v4.
Naturally, I wouldn't be at all opposed to you or any other maintainer
making such a small change to one of my patches as it heads upstream,
but I'd rather not ask you to remember to make that change after a long
vacation and a busy merge window. There's no need for me to add even a
little more cognitive load to your job than what's necessary.
> Speaking of applying this, I'll be on vacation next week, so I won't
> be able to apply the patches until the week after. That will also give
> anyone else on the list a chance to comment if they want...
Awesome! I'll plan to sit tight and act on whatever feedback I get on
v4.
If you happen to be flying over northern Utah to get to your
destination, look out the window. I'll wave as you go by.
Cheers,
Brigham
Powered by blists - more mailing lists