From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Sunyun Yang <syyang@lontium.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andrzej.hajda@intel.com, neil.armstrong@linaro.org,
maarten.lankhorst@linux.intel.com, rfoss@kernel.org,
mripard@kernel.org, Laurent.pinchart@ideasonboard.com,
tzimmermann@suse.de, jonas@kwiboo.se, jernej.skrabec@gmail.com,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
xmzhu@lontium.corp-partner.google.com, xmzhu@lontium.com,
rlyu@lontium.com, xbpeng@lontium.com
Subject: Re: [PATCH v6 1/2] dt-bindings: bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver
Date: Wed, 13 May 2026 14:23:47 +0300 [thread overview]
Message-ID: <b951a99a-bddf-4fe7-8ed0-4861d93aaf4e@oss.qualcomm.com> (raw)
In-Reply-To: <CAFQXuNb8w-+xEYeDSxaqK-2hxdu5ADo_Vtvy4iVBzSgNzRmSuw@mail.gmail.com>
On 13/05/2026 14:22, Sunyun Yang wrote:
> Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> 于2026年5月13日周三 19:10写道：
>>
>> On 13/05/2026 14:07, Sunyun Yang wrote:
>>> Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> 于2026年5月13日周三 18:24写道：
>>>>
>>>> On Mon, May 11, 2026 at 11:28:06AM +0800, Sunyun Yang wrote:
>>>>> <syyang@lontium.com> 于2026年5月8日周五 22:25写道：
>>>>>>
>>>>>> From: Sunyun Yang <syyang@lontium.com>
>>>>>
>>>>> Gentle ping.
>>>>> Thanks.
>>>>
>>>> You've posted the bindings on May 8th. Please give maintainers some time
>>>> to react. Not to mention that you posting the bindings 4 times in a row
>>>> (once together with the driver and other 3 times separately) doesn't
>>>> help maintainers.
>>>>
>>> Sorry, when I submitted the patch on May 8th, I received bounce
>>> notifications from devicetree@vger.kernel.org and conor+dt@kernel.org,
>>> which is why I sent the patch again.
>>
>> And some patch trackers will now have incomplete series, others will
>> have duplicate entries, etc.
>>
>> In future please use `b4 --resend` to resend the whole series at once.
>>
>
> Isn't it recommended not to use 'git send-email' ?
The 'b4' tool is generally recommended over raw usage of 'git
send-email'. It saves you from some of the troubles and catches several
typical errors.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2026-05-13 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 14:25 [PATCH v6 1/2] dt-bindings: bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver syyang
2026-05-11 3:28 ` Sunyun Yang
2026-05-13 10:24 ` Dmitry Baryshkov
2026-05-13 11:07 ` Sunyun Yang
2026-05-13 11:10 ` Dmitry Baryshkov
2026-05-13 11:22 ` Sunyun Yang
2026-05-13 11:23 ` Dmitry Baryshkov [this message]
2026-05-13 11:35 ` Sunyun Yang
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=b951a99a-bddf-4fe7-8ed0-4861d93aaf4e@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=rlyu@lontium.com \
--cc=robh@kernel.org \
--cc=syyang@lontium.com \
--cc=tzimmermann@suse.de \
--cc=xbpeng@lontium.com \
--cc=xmzhu@lontium.com \
--cc=xmzhu@lontium.corp-partner.google.com \
/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