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]
Message-ID: <20200504085608.GR1375924@vkoul-mobl>
Date:   Mon, 4 May 2020 14:26:08 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Cristian Ciocaltea <cristian.ciocaltea@...il.com>
Subject: Re: linux-next: Fixes tag needs some work in the slave-dma-fixes tree

On 04-05-20, 18:53, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   c76d6569de67 ("dmaengine: owl: Use correct lock in owl_dma_get_pchan()")
> 
> Fixes tag
> 
>   Fixes: 47e20577c24d ("dmaengine: Add Actions Semi Owl family S900 DMA
> 
> 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.

Updated and pushed out, thanks for notifying

-- 
~Vinod

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ