From: Mihai Moldovan <ionic@ionic.de>
To: ath11k@lists.infradead.org
Subject: Re: State of multiple PCI(e) modules since 2022
Date: Fri, 1 Nov 2024 18:17:30 +0100 [thread overview]
Message-ID: <a7954fb4-4f3f-4923-8d50-a04891037d3f@ionic.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 558 bytes --]
* On 11/1/24 18:05, Mihai Moldovan wrote:
> [...]
Sorry, my mail client crashed while composing the message and continuing the
draft didn't automatically include the In-Reply-To or References headers.
Unfortunately I only noticed that after receiving a copy of my message back from
the list. I didn't intend to break the original thread. I'm aware that this is
highly annoying.
I'll be more careful in the future and will manually supply an In-Reply-To
header now that I'm aware of the issues with continuing a draft message.
Mihai
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2024-11-01 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 17:17 Mihai Moldovan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 17:05 State of multiple PCI(e) modules since 2022 Mihai Moldovan
2024-10-27 14:11 Mihai Moldovan
2024-10-29 16:39 ` Denis Kenzior
2024-10-31 14:49 ` Jeff Johnson
2024-11-05 6:52 ` Mihai Moldovan
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=a7954fb4-4f3f-4923-8d50-a04891037d3f@ionic.de \
--to=ionic@ionic.de \
--cc=ath11k@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox