From: Dan Carpenter <dan.carpenter@linaro.org>
To: bubupersonal@tutamail.com
Cc: Linux Staging <linux-staging@lists.linux.dev>,
Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] rtw: btcoex: clean up style and documentation
Date: Fri, 6 Feb 2026 10:43:18 +0300 [thread overview]
Message-ID: <aYWblhoLbSYCHkwH@stanley.mountain> (raw)
In-Reply-To: <OkisUHh--F-9@tutamail.com>
On Thu, Feb 05, 2026 at 06:38:06PM +0100, bubupersonal@tutamail.com wrote:
> Here's the correct patch.
Nope. That's not a patch.
regards,
dan carpenter
prev parent reply other threads:[~2026-02-06 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 16:18 [PATCH] rtw: btcoex: clean up style and documentation bubupersonal
2026-02-05 16:42 ` Greg KH
[not found] ` <OkipX2h--N-9@tutamail.com>
[not found] ` <2026020533-commotion-surfacing-e9ea@gregkh>
2026-02-05 17:38 ` bubupersonal
2026-02-06 7:43 ` Dan Carpenter [this message]
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=aYWblhoLbSYCHkwH@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=bubupersonal@tutamail.com \
--cc=linux-staging@lists.linux.dev \
--cc=linux-wireless@vger.kernel.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