From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Clark <robdclark@gmail.com>,
Sean Paul <seanpaul@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the drm-msm tree
Date: Wed, 2 Mar 2022 05:32:56 +0300 [thread overview]
Message-ID: <CAA8EJpojNFKB2u6KrfotYUyRfqXjKbwQfdaz1dJ7N=2M7cQA_w@mail.gmail.com> (raw)
In-Reply-To: <20220302114312.077aa81b@canb.auug.org.au>
On Wed, 2 Mar 2022 at 03:43, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> 8661f450626f ("dt-bindings: display/msm: add missing brace in dpu-qcm2290.yaml")
>
> Fixes tag
>
> Fixes: 164f69d9d45a ("dt-bindings: msm: disp: add yaml schemas for
It seems the Fixes tag got split by my mail client.
Rob, any chance to fix that?
>
> has these problem(s):
>
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
>
> Please do not split Fixes tags over moe than one line or truncate them.
>
> --
> Cheers,
> Stephen Rothwell
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-03-02 2:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 0:43 linux-next: Fixes tag needs some work in the drm-msm tree Stephen Rothwell
2022-03-02 2:32 ` Dmitry Baryshkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-01 22:42 Stephen Rothwell
2022-05-01 22:39 Stephen Rothwell
2022-05-01 22:35 Stephen Rothwell
2021-10-04 21:25 Stephen Rothwell
2021-10-04 21:23 Stephen Rothwell
2021-06-17 22:32 Stephen Rothwell
2021-05-25 0:27 Stephen Rothwell
2021-05-08 2:16 Stephen Rothwell
2020-12-06 20:05 Stephen Rothwell
2020-12-06 21:05 ` Iskren Chernev
2020-12-06 21:57 ` Stephen Rothwell
2020-12-06 22:00 ` Stephen Rothwell
2020-11-04 20:41 Stephen Rothwell
2020-07-30 22:28 Stephen Rothwell
2020-07-16 0:25 Stephen Rothwell
2020-07-14 0:02 Stephen Rothwell
2020-06-12 4:10 Stephen Rothwell
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='CAA8EJpojNFKB2u6KrfotYUyRfqXjKbwQfdaz1dJ7N=2M7cQA_w@mail.gmail.com' \
--to=dmitry.baryshkov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.org \
--cc=sfr@canb.auug.org.au \
/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).