Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <ccaa1df9-279e-e3a5-514e-e3baebb03357@schmorgal.com>
Date:   Mon, 7 Nov 2022 12:00:50 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.1
Content-Language: en-US
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Vinod Koul <vkoul@kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20221107183054.7007fd7a@canb.auug.org.au>
From:   Doug Brown <doug@schmorgal.com>
Subject: Re: linux-next: Fixes tag needs some work in the dmaengine tree
In-Reply-To: <20221107183054.7007fd7a@canb.auug.org.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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