linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: Fixes tag needs some work in the drm tree
@ 2019-02-04  5:50 Stephen Rothwell
  0 siblings, 0 replies; 11+ messages in thread
From: Stephen Rothwell @ 2019-02-04  5:50 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Nicholas Kazlauskas, Alex Deucher

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

Hi all,

In commit

  4b5105036afb ("drm/amd/display: Don't leak memory when updating streams")

Fixes tags

  Fixes: c00e0cc0fdc0 ("drm/amd/display: Call into DC once per multiplane flip")
  Fixes: ea39594e0855 ("drm/amd/display: Perform plane updates only when needed")

have this problem:

  - Target SHA1s do not exist

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* linux-next: Fixes tag needs some work in the drm tree
@ 2022-09-11 22:54 Stephen Rothwell
  0 siblings, 0 replies; 11+ messages in thread
From: Stephen Rothwell @ 2022-09-11 22:54 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Melissa Wen, Alex Deucher, Linux Kernel Mailing List,
	Linux Next Mailing List

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

Hi all,

In commit

  89b03aeaef16 ("drm/vkms: fix 32bit compilation error by replacing macros")

Fixes tag

  Fixes: a19c2ac9858 ("drm: vkms: Add support to the RGB565 format")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: 396369d67549 ("drm: vkms: Add support to the RGB565 format")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* linux-next: Fixes tag needs some work in the drm tree
@ 2022-07-12 11:27 Stephen Rothwell
  0 siblings, 0 replies; 11+ messages in thread
From: Stephen Rothwell @ 2022-07-12 11:27 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Alex Deucher, Linux Kernel Mailing List, Linux Next Mailing List

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

Hi all,

In commit

  d8e4fb9112e8 ("drm/amdgpu/display: Protect some functions with CONFIG_DRM_AMD_DC_DCN")

Fixes tag

  Fixes: 9b0e0d433f74 ("drm/amd/display: Add dependant changes for DCN32/321")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant:

Fixes: d3dfceb58de5 ("drm/amd/display: Add dependant changes for DCN32/321")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-next: Fixes tag needs some work in the drm tree
  2022-06-04  0:37   ` Stephen Rothwell
@ 2022-06-04  1:12     ` Rob Clark
  0 siblings, 0 replies; 11+ messages in thread
From: Rob Clark @ 2022-06-04  1:12 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Rob Clark, Dave Airlie, Linux Next Mailing List, Haowen Bai,
	Abhinav Kumar, DRI, Linux Kernel Mailing List

On Fri, Jun 3, 2022 at 5:38 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Rob,
>
> On Fri, 3 Jun 2022 07:58:14 -0700 Rob Clark <robdclark@gmail.com> wrote:
> >
> > will the truncated subject confuse the scripts that look for patches
> > to backport to stable, ie. do we *really* have to rewrite history to
> > fix this?
>
> I don't know what scripts are being used and what they expect, but our
> documentation says (Documentation/process/submitting-patches.rst):
>
>   If your patch fixes a bug in a specific commit, e.g. you found an issue using
>   ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
>   the SHA-1 ID, and the one line summary.  Do not split the tag across multiple
>   lines, tags are exempt from the "wrap at 75 columns" rule in order to simplify
>   parsing scripts.
>
> But, that being said, doing the rewrite is up to the maintainer.  You
> could just look at this as a learning experience and do better in the
> future.

Ok, I'll leave it up to airlied

If you don't mind sharing, what is the script you use?  We could
perhaps add it to our WIP CI..  a script is much less likely to miss a
check than a human, so I'm a fan of automating these sorts of checks
whenever possible ;-)

BR,
-R

> BTW, my script reacted to the missing closing quotes and parentheses,
> which is more like to confuse any scripts that the actual truncation.
> --
> Cheers,
> Stephen Rothwell

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-next: Fixes tag needs some work in the drm tree
  2022-06-03 14:58 ` Rob Clark
@ 2022-06-04  0:37   ` Stephen Rothwell
  2022-06-04  1:12     ` Rob Clark
  0 siblings, 1 reply; 11+ messages in thread
From: Stephen Rothwell @ 2022-06-04  0:37 UTC (permalink / raw)
  To: Rob Clark
  Cc: Dave Airlie, Linux Next Mailing List, Haowen Bai, Abhinav Kumar,
	DRI, Linux Kernel Mailing List, Rob Clark

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

Hi Rob,

On Fri, 3 Jun 2022 07:58:14 -0700 Rob Clark <robdclark@gmail.com> wrote:
>
> will the truncated subject confuse the scripts that look for patches
> to backport to stable, ie. do we *really* have to rewrite history to
> fix this?

I don't know what scripts are being used and what they expect, but our
documentation says (Documentation/process/submitting-patches.rst):

  If your patch fixes a bug in a specific commit, e.g. you found an issue using
  ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
  the SHA-1 ID, and the one line summary.  Do not split the tag across multiple
  lines, tags are exempt from the "wrap at 75 columns" rule in order to simplify
  parsing scripts.

But, that being said, doing the rewrite is up to the maintainer.  You
could just look at this as a learning experience and do better in the
future.

BTW, my script reacted to the missing closing quotes and parentheses,
which is more like to confuse any scripts that the actual truncation.
-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-next: Fixes tag needs some work in the drm tree
  2022-06-03  5:16 Stephen Rothwell
@ 2022-06-03 14:58 ` Rob Clark
  2022-06-04  0:37   ` Stephen Rothwell
  0 siblings, 1 reply; 11+ messages in thread
From: Rob Clark @ 2022-06-03 14:58 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Dave Airlie, Linux Next Mailing List, Haowen Bai, Abhinav Kumar,
	DRI, Linux Kernel Mailing List, Rob Clark

On Thu, Jun 2, 2022 at 10:16 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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")

Hmm, checkpatch seems to not catch this (unless it was a recent
addition that landed after what msm-fixes is based on.

will the truncated subject confuse the scripts that look for patches
to backport to stable, ie. do we *really* have to rewrite history to
fix this?

BR,
-R

^ permalink raw reply	[flat|nested] 11+ messages in thread

* linux-next: Fixes tag needs some work in the drm tree
@ 2022-06-03  5:16 Stephen Rothwell
  2022-06-03 14:58 ` Rob Clark
  0 siblings, 1 reply; 11+ messages in thread
From: Stephen Rothwell @ 2022-06-03  5:16 UTC (permalink / raw)
  To: Dave Airlie
  Cc: DRI, Haowen Bai, Abhinav Kumar, Linux Kernel Mailing List,
	Linux Next Mailing List

[-- 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 --]

^ permalink raw reply	[flat|nested] 11+ messages in thread

* RE: linux-next: Fixes tag needs some work in the drm tree
  2019-10-27 20:23 Stephen Rothwell
@ 2019-10-28  4:09 ` S, Shirish
  0 siblings, 0 replies; 11+ messages in thread
From: S, Shirish @ 2019-10-28  4:09 UTC (permalink / raw)
  To: Stephen Rothwell, Dave Airlie, DRI
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Deucher, Alexander

Yes, that's what it meant.



Regards,
Shirish S

-----Original Message-----
From: Stephen Rothwell <sfr@canb.auug.org.au> 
Sent: Monday, October 28, 2019 1:53 AM
To: Dave Airlie <airlied@linux.ie>; DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; S, Shirish <Shirish.S@amd.com>; Deucher, Alexander <Alexander.Deucher@amd.com>
Subject: linux-next: Fixes tag needs some work in the drm tree

Hi all,

In commit

  8c9f69bc5cc4 ("drm/amdgpu: fix build error without CONFIG_HSA_AMD")

Fixes tag

  Fixes: 1abb680ad371 ("drm/amdgpu: disable gfxoff while use no H/W scheduling policy")

has these problem(s):

  - Target SHA1 does not exist

Did you mean:

Fixes: aa978594cf7f ("drm/amdgpu: disable gfxoff while use no H/W scheduling policy")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 11+ messages in thread

* linux-next: Fixes tag needs some work in the drm tree
@ 2019-10-27 20:23 Stephen Rothwell
  2019-10-28  4:09 ` S, Shirish
  0 siblings, 1 reply; 11+ messages in thread
From: Stephen Rothwell @ 2019-10-27 20:23 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Shirish S,
	Alex Deucher

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

Hi all,

In commit

  8c9f69bc5cc4 ("drm/amdgpu: fix build error without CONFIG_HSA_AMD")

Fixes tag

  Fixes: 1abb680ad371 ("drm/amdgpu: disable gfxoff while use no H/W scheduling policy")

has these problem(s):

  - Target SHA1 does not exist

Did you mean:

Fixes: aa978594cf7f ("drm/amdgpu: disable gfxoff while use no H/W scheduling policy")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* linux-next: Fixes tag needs some work in the drm tree
@ 2019-07-19  8:41 Stephen Rothwell
  0 siblings, 0 replies; 11+ messages in thread
From: Stephen Rothwell @ 2019-07-19  8:41 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Ilia Mirkin,
	Ben Skeggs

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

Hi all,

In commit

  b7019ac550eb ("drm/nouveau: fix bogus GPL-2 license header")

Fixes tag

  Fixes: b24413180f5 (License cleanup: add SPDX GPL-2.0 license identifier to files with no license)

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* linux-next: Fixes tag needs some work in the drm tree
@ 2019-03-04  8:09 Stephen Rothwell
  0 siblings, 0 replies; 11+ messages in thread
From: Stephen Rothwell @ 2019-03-04  8:09 UTC (permalink / raw)
  To: Dave Airlie, DRI
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Mario Kleiner, Nicholas Kazlauskas, Alex Deucher

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

Hi all,

In commit

  289aabbf7bc8 ("drm/amd/display: Use vrr friendly pageflip throttling in DC.")

Fixes tag

  Fixes: bb47de736661 ("drm/amdgpu: Set FreeSync state using drm VRR

has these problem(s):

  - Please don't split Fixes tags over more than one line

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2022-09-11 23:02 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-04  5:50 linux-next: Fixes tag needs some work in the drm tree Stephen Rothwell
2019-03-04  8:09 Stephen Rothwell
2019-07-19  8:41 Stephen Rothwell
2019-10-27 20:23 Stephen Rothwell
2019-10-28  4:09 ` S, Shirish
2022-06-03  5:16 Stephen Rothwell
2022-06-03 14:58 ` Rob Clark
2022-06-04  0:37   ` Stephen Rothwell
2022-06-04  1:12     ` Rob Clark
2022-07-12 11:27 Stephen Rothwell
2022-09-11 22:54 Stephen Rothwell

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).