linux-kernel - Re: [RESEND PATCH] w1: Add missing newline and fix typos in w1_bus

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: <6310dd93-2e4a-4b80-85a9-2439bad15e1e@kernel.org>
Date: Wed, 29 May 2024 12:53:35 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Thorsten Blum <thorsten.blum@...lux.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH] w1: Add missing newline and fix typos in
 w1_bus_master comment

On 29/05/2024 12:29, Thorsten Blum wrote:
> On 27. May 2024, at 13:49, Krzysztof Kozlowski <krzk@...nel.org> wrote:
>> On 27/05/2024 11:27, Thorsten Blum wrote:
>>> - Add missing newline before @return
>>> - s/bytes/byte/
>>> - s/handles/handle/
>>>
>>> Signed-off-by: Thorsten Blum <thorsten.blum@...lux.com>
>>
>> Do not attach (thread) your patchsets to some other threads (unrelated
>> or older versions). This buries them deep in the mailbox and might
>> interfere with applying entire sets.
>>
>>
>> Applying: w1: Add missing newline and fix typos in w1_bus_master comment
>> Applying: w1: Add missing newline and fix typos in w1_bus_master comment
>> Patch failed at 0002 w1: Add missing newline and fix typos in
>> w1_bus_master comment
>> When you have resolved this problem, run "git am --continue".
>> If you prefer to skip this patch, run "git am --skip" instead.
>> To restore the original branch and stop patching, run "git am --abort".
>> error: patch failed: include/linux/w1.h:85
>> error: include/linux/w1.h: patch does not apply
>> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> 
> Hi Krzysztof,
> 
> just to clarify: do you want me to submit the patch again or did you run 
> "git am --skip" to skip the identical, but threaded resend?

I run --skip, so patch is there. Should be already in the next. You just
don't get notification email, because `b4 ty` does not mark such case as
applied. No need for resend.

Best regards,
Krzysztof