From: Kalle Valo <kvalo@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: trix@redhat.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ath9k: initialize arrays at compile time
Date: Mon, 28 Mar 2022 17:17:53 +0300 [thread overview]
Message-ID: <87pmm6xisu.fsf@kernel.org> (raw)
In-Reply-To: <87lewu5fw7.fsf@toke.dk> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\= \=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of "Mon, 28 Mar 2022 16:08:08 +0200")
Toke Høiland-Jørgensen <toke@toke.dk> writes:
> Kalle Valo <kvalo@kernel.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
next prev parent reply other threads:[~2022-03-28 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 13:07 [PATCH v2] ath9k: initialize arrays at compile time trix
2022-03-28 13:39 ` Kalle Valo
2022-03-28 14:08 ` Toke Høiland-Jørgensen
2022-03-28 14:17 ` Kalle Valo [this message]
2022-03-28 15:45 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmm6xisu.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@toke.dk \
--cc=trix@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.