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: <87pmm6xisu.fsf@kernel.org>
Date:   Mon, 28 Mar 2022 17:17:53 +0300
From:   Kalle Valo <kvalo@...nel.org>
To:     Toke Høiland-Jørgensen <toke@...e.dk>
Cc:     trix@...hat.com, 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

Toke Høiland-Jørgensen <toke@...e.dk> writes:

> 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

Heh, strange.

> 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?

Yeah, I'm using Gnus which is pretty exotic :) It might be choosing
octet-stream for me.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches