2022-11-07 08:11:51

by Stephen Rothwell

[permalink] [raw]
Subject: linux-next: Fixes tag needs some work in the dmaengine tree

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

--
Cheers,
Stephen Rothwell

Attachments:
(No filename) (499.00 B)
OpenPGP digital signature

2022-11-07 20:42:57

by Doug Brown

[permalink] [raw]
Subject: Re: linux-next: Fixes tag needs some work in the dmaengine tree

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?

Thanks,
Doug

2022-11-08 05:45:04

by Vinod Koul

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