From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Rostislav Lisovy <lisovy@gmail.com>,
Linux Wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>
Subject: Re: Old WiFi modules -- for testing?
Date: Sun, 22 Oct 2023 21:09:04 +0700 [thread overview]
Message-ID: <872e8be6-c0d0-4e5f-94d8-e5c021d24585@gmail.com> (raw)
In-Reply-To: <d85050999a2944a921a38352d1c371fdb3b8c29e.camel@gmail.com>
On 22/10/2023 19:31, Rostislav Lisovy wrote:
> Unfortunately I do not have any further info than what is on the
> pictures.
>
I'm confused then...
Anyway, you can try submitting patches as contributor (see
Documentation/process/submitting-patches.rst for details).
Bye!
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-10-22 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ca929e1d8197ace414a06b20151b84de3dd160f4.camel@gmail.com>
2023-10-22 11:31 ` Old WiFi modules -- for testing? Bagas Sanjaya
2023-10-22 12:31 ` Rostislav Lisovy
2023-10-22 14:09 ` Bagas Sanjaya [this message]
2023-10-22 14:17 ` Rostislav Lisovy
2023-10-22 23:29 ` Bagas Sanjaya
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=872e8be6-c0d0-4e5f-94d8-e5c021d24585@gmail.com \
--to=bagasdotme@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lisovy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox