From: Ping-Ke Shih <pkshih@realtek.com>
To: ZeroBeat <ZeroBeat@gmx.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>
Subject: RE: [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID
Date: Fri, 8 Dec 2023 00:43:37 +0000 [thread overview]
Message-ID: <d654be3682e545d09bc7ca7a91e1b58a@realtek.com> (raw)
In-Reply-To: <09b41f73-33c9-4c82-82ad-09c51840149f@gmx.de>
> -----Original Message-----
> From: ZeroBeat <ZeroBeat@gmx.de>
> Sent: Thursday, December 7, 2023 5:39 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: linux-wireless@vger.kernel.org; Jes.Sorensen@gmail.com
> Subject: Re: [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID
>
> Is this correct to commit inline patches?
> Looks for me similar to this one
> https://lore.kernel.org/linux-wireless/20231127162022.518834-2-kvalo@kernel.org/T/#u
>
The basic steps to submit a patch are:
1. add this patch to wireless-next tree locally
2. git format-patch -1
3. run ./scripts/checkpatch.pl with your patch and fix warnings
4. git send-email to send out the patch.
With above steps, your patch would be much similar to others.
More detail can reference Documentation/process/submitting-patches.rst and
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-08 0:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 8:46 [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID ZeroBeat
2023-12-07 8:52 ` Ping-Ke Shih
2023-12-07 9:02 ` ZeroBeat
2023-12-07 9:38 ` ZeroBeat
2023-12-08 0:43 ` Ping-Ke Shih [this message]
2023-12-08 6:41 ` ZeroBeat
2023-12-08 7:01 ` Ping-Ke Shih
2023-12-08 7:37 ` ZeroBeat
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 11:48 ZeroBeat
2023-12-07 0:17 ` Ping-Ke Shih
2023-12-07 11:51 ` ZeroBeat
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=d654be3682e545d09bc7ca7a91e1b58a@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=ZeroBeat@gmx.de \
--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 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.