netdev - Re: [PATCH net-next v6] net: sched: Introduce act

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <70B35849-D2D4-4B4E-8D3E-8AF089B0947F@darbyshire-bryant.me.uk>
Date:   Tue, 28 May 2019 18:52:32 +0000
From:   Kevin 'ldir' Darbyshire-Bryant <ldir@...byshire-bryant.me.uk>
To:     Toke Høiland-Jørgensen <toke@...hat.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v6] net: sched: Introduce act_ctinfo action

> On 28 May 2019, at 19:08, Toke Høiland-Jørgensen <toke@...hat.com> wrote:
> 
<stuff snipped>
> 
> Thank you for doing another iteration!
> 
> No further comments on the actual code, but I still get the whitespace
> issue with the patch... And now it results in stray ^M characters in the
> Kconfig file, which makes the build blow up :/

This is very odd.  I produced the last patch (v6) from within a debian VM
and sent it from there also.  No weird line endings in the locally produced
patch text and it applied cleanly to a local tree.  I’ve sent test patches
into the openwrt tree and applied those cleanly direct from patchwork.

Similarly I’ve downloaded the v5 patch from netdev patchwork http://patchwork.ozlabs.org/patch/1105755/mbox/ and applied that with git
am without problem.

Am totally confused!

Cheers,

Kevin D-B

gpg: 012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A