linux-kernel - Re: [GIT PULL] interconnect changes for 5.20

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]

Date:   Sat, 16 Jul 2022 08:49:56 +0300
From:   Georgi Djakov <djakov@...nel.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] interconnect changes for 5.20


On 16.07.22 8:21, Greg KH wrote:
> On Fri, Jul 15, 2022 at 06:30:36PM +0300, Georgi Djakov wrote:
>>
>> On 15.07.22 15:54, Greg KH wrote:
>>> On Fri, Jul 15, 2022 at 02:53:13PM +0200, Greg KH wrote:
>>>> On Fri, Jul 15, 2022 at 01:10:21PM +0300, Georgi Djakov wrote:
>>>>> Hello Greg,
>>>>>
>>>>> This is the pull request with interconnect changes for the 5.20-rc1 merge
>>>>> window. It contains driver updates. The details are in the signed tag.
>>>>>
>>>>> All patches have been in linux-next during the last few days. No issues have
>>>>> been reported so far. Please pull into char-misc-next.
>>>>>
>>>>> Thanks,
>>>>> Georgi
>>>>>
>>>>> The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
>>>>>
>>>>>     Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
>>>>>
>>>>> are available in the Git repository at:
>>>>>
>>>>>     git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git tags/icc-5.20-rc1
>>>>
>>>> Pulled and pushed out, thanks.
>>>
>>> Oops, nope, I got the following error:
>>>
>>> Fixes tag: Fixes: f0d8048525d7d("interconnect: Add imx core driver")
>>> 	Has these problem(s):
>>> 		- missing space between the SHA1 and the subject
>>>
>>
>> Apologies for missing this. This was in linux-next for more than a week, but nobody
>> reported it. I'll create a script to check for this problem to my workflow.
>> Now sending you v2 pull request.
> 
> That's odd, as my scripts come from Stephen's linux-next scripts, I
> would have thought he would have caught it before me.

I also thought the same, but anyway, now added your verify_fixes.sh checks to my workflow.

Thanks,
Georgi