linux-kernel - Re: linux-next: Fixes tag needs some work in the omap-fixes tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <773CBF24-F8B7-481F-BBCE-53C13198FBED@goldelico.com>
Date:   Wed, 13 Apr 2022 08:21:18 +0200
From:   "H. Nikolaus Schaller" <hns@...delico.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Tony Lindgren <tony@...mide.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the omap-fixes tree

Hi Stephen,

> Am 12.04.2022 um 23:02 schrieb Stephen Rothwell <sfr@...b.auug.org.au>:
> 
> Hi all,
> 
> In commit
> 
>  9be24a73de12 ("ARM: dts: Fix mmc order for omap3-gta04")
> 
> Fixes tag
> 
>  Fixes: commit a1ebdb374199 ("ARM: dts: Fix swapped mmc order for omap3")
> 
> has these problem(s):
> 
>  - leading word 'commit' unexpected

Ah, I see.
Diff of patch is good but the commit message needs editing.

What is the procedure to fix this case?

BR and thanks,
Nikolaus