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: <Y2nmDQYfrMvlVYwV@matsya>
Date:   Tue, 8 Nov 2022 10:45:57 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Doug Brown <doug@...morgal.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        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 dmaengine tree

On 07-11-22, 12:00, Doug Brown wrote:
> Hi Stephen and Vinod,
> 
> On 11/6/2022 11:30 PM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > In commit
> > 
> >    639d91b2d4c8 ("dmaengine: pxa_dma: use platform_get_irq_optional")
> > 
> > Fixes tag
> > 
> >    Fixes: 7723f4c5ecdb ("driver core: platform: Add an error message to platform_get_irq*()"
> > 
> > has these problem(s):
> > 
> >    - Subject has leading but no trailing quotes
> > 
> > Actually, it looks like it is missing the closeing ')'.
> > 
> 
> Dang it, I'm sorry. I don't know how I messed that up. I'm not familiar
> with the process for fixing this after it's already been accepted into
> the dmaengine tree -- should I just submit a V2 patch with this fixed?

I have fixed it up...

-- 
~Vinod

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ