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: <20190502165530.GJ19809@lunn.ch>
Date:   Thu, 2 May 2019 18:55:30 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     David Miller <davem@...emloft.net>,
        Florian Fainelli <f.fainelli@...il.com>,
        vivien.didelot@...il.com, netdev <netdev@...r.kernel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 net-next 00/12] NXP SJA1105 DSA driver

> Wow I am sorry, Gmail apparently moved your reply to spam and I only
> got it when I posted my message just now.
> Do you know what causes these whitespace errors, so I can avoid them
> next time? I think I'm generating my patches rather normally, with
> $(git format-patch -12 --subject-prefix="PATCH v4 net-next"
> --cover-letter).

What happens when you run checkpatch on the patches? Does it report
white space problems.

Another possibility is your email system has mangled the patches.
First try applying the patches you generated from format-patch to a
clean tree. If you don't get any warnings, email the patches to
yourself, and then apply them.

     Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ