From: Vinod Koul <vkoul@kernel•org>
To: "Csókás Bence" <csokas.bence@prolan•hu>,
"Vinod Koul" <vkoul@kernel•org>,
"Stephen Rothwell" <sfr@canb•auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the dmaengine tree
Date: Wed, 11 Dec 2024 17:36:32 +0530 [thread overview]
Message-ID: <6aa70be5-59d0-4441-9432-79cb87fdd915@kernel.org> (raw)
In-Reply-To: <2e61add7-8e72-4ef4-b696-8bb5c0e83d01@prolan.hu>
On 11/12/24 14:39, Csókás Bence wrote:
> Hi,
>
> On 2024. 12. 10. 17:58, Vinod Koul wrote:
>> On 09-12-24, 07:50, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Commit
>>>
>>> 1ad2ebf3be83 ("dt-bindings: dmaengine: Add Allwinner suniv F1C100s
>>> DMA")
>>>
>>> is missing a Signed-off-by from its author.
>>>
>>> Scripting confused by the comma in the origin SoB line?
>>
>> Yes I guess so, checked again yes b4 seems to eat it up
>>
>>>
>>> Also, please keep all the commit message tags together at the end of
>>> the commit message.
>>
>> Again scripting is going bonkers here
>>
>> I have fixed it up now
>>
>
> Still broken in these:
>
> commit eeca1b601381 ("dma-engine: sun4i: Add a quirk to support
> different chips")
> commit 1f738d0c2f67 ("dma-engine: sun4i: Add has_reset option to quirk")
Fixed all.. looks like all patches from you have this issue :-(
--
~Vinod
prev parent reply other threads:[~2024-12-11 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 20:50 linux-next: Signed-off-by missing for commit in the dmaengine tree Stephen Rothwell
2024-12-10 16:58 ` Vinod Koul
2024-12-11 9:09 ` Csókás Bence
2024-12-11 12:06 ` Vinod Koul [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6aa70be5-59d0-4441-9432-79cb87fdd915@kernel.org \
--to=vkoul@kernel$(echo .)org \
--cc=csokas.bence@prolan$(echo .)hu \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox