linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>
Cc: DRI <dri-devel@lists.freedesktop.org>,
	Haowen Bai <baihaowen@meizu.com>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the drm tree
Date: Fri, 3 Jun 2022 15:16:00 +1000	[thread overview]
Message-ID: <20220603151600.19cfa617@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

Hi all,

In commit

  8caad14e7224 ("drm/msm/dpu: Fix pointer dereferenced before checking")

Fixes tag

  Fixes: d7d0e73f7de33 ("drm/msm/dpu: introduce the dpu_encoder_phys_* for

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes

Fixes tags should not be truncated or split across more than 1 line.   So:

Fixes: d7d0e73f7de3 ("drm/msm/dpu: introduce the dpu_encoder_phys_* for writeback")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-06-03  5:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  5:16 Stephen Rothwell [this message]
2022-06-03 14:58 ` linux-next: Fixes tag needs some work in the drm tree Rob Clark
2022-06-04  0:37   ` Stephen Rothwell
2022-06-04  1:12     ` Rob Clark
  -- strict thread matches above, loose matches on Subject: below --
2022-09-11 22:54 Stephen Rothwell
2022-07-12 11:27 Stephen Rothwell
2019-10-27 20:23 Stephen Rothwell
2019-10-28  4:09 ` S, Shirish
2019-07-19  8:41 Stephen Rothwell
2019-03-04  8:09 Stephen Rothwell
2019-02-04  5:50 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=20220603151600.19cfa617@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=baihaowen@meizu.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=quic_abhinavk@quicinc.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;
as well as URLs for NNTP newsgroup(s).