netdev - Re: [PATCH v2] ath9k: initialize arrays at compile time

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: <87lewu5fw7.fsf@toke.dk>
Date:   Mon, 28 Mar 2022 16:08:08 +0200
From:   Toke Høiland-Jørgensen <toke@...e.dk>
To:     Kalle Valo <kvalo@...nel.org>, trix@...hat.com
Cc:     davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ath9k: initialize arrays at compile time

Kalle Valo <kvalo@...nel.org> writes:

> Hi,
>
> The content type on this email was weird:
>
> Content-Type: application/octet-stream; x-default=true

Hmm, I get:

Content-Type: text/plain; charset="US-ASCII"; x-default=true

Patchwork seems to have parsed the content just fine, but it shows *no*
content-type, so maybe the issue is that the header is missing but
different systems repair that differently?

-Toke