linux-kernel - Re: linux-next: Fixes tag needs some work in the sound-asoc 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] [day] [month] [year] [list]

Date:   Thu, 28 Apr 2022 11:04:04 +0800
From:   Tinghan Shen <tinghan.shen@...iatek.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>
CC:     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 sound-asoc tree

Hi Stephen,

On Thu, 2022-04-28 at 10:57 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   9ce170dc9c08 ("ASoC: SOF: mediatek: Fix allyesconfig build error")
> 
> Fixes tag
> 
>   Fixes: 570c14dc92d5 ("ASoC: SOF: mediatek: Add mt8186 sof fw loader and
> 
> 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 more than one line.  Also, please keep
> all the commit message tags together at the end of the commit message.
> 
> This whole commit message was badly word wrapped :-(

It's because I want to keep the original build message and 
wrap at the 75 columns at the same time. After look back of
your ealier email, I should refrain from doing so and leave the 
build message unwrapped, as you did.

I apologize for the fault, I'll keep this in my mind.


Thanks,
TingHan