Received-SPF: pass (google.com: domain of linux-wireless+bounces-574-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Message-ID: <a6a23ccf-b571-49bf-855b-4fba3501f09b@gmx.de>
Date: Fri, 8 Dec 2023 07:41:59 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
 "Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>
References: <415ecdaf-eebc-4a9e-9053-4cc999711ad7@gmx.de>
 <c81f09d43fab416ba7233dd9d5cfcd2d@realtek.com>
 <09b41f73-33c9-4c82-82ad-09c51840149f@gmx.de>
 <d654be3682e545d09bc7ca7a91e1b58a@realtek.com>
Content-Language: en-US
From: ZeroBeat <ZeroBeat@gmx.de>
Subject: Re: [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID
In-Reply-To: <d654be3682e545d09bc7ca7a91e1b58a@realtek.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
UI-OutboundReport: notjunk:1;M01:P0:GJem9NalXpU=;aOxvKBDYazYtHgyyJFaWcsurrSt
 LUjXUMWNsc90DbTRmi4TFyPNxF3JOjNqR53smoL2d2PFdJI19De1djUDXbM7EvdQxROmdY3qn
 OrFegLX/UxEYgkXzBy6qdqKOj+C6p2aa958onKWByLuwqQMOhi69qzQ1acf9QICRgQf8q/7uL
 AJhxykxG+o7sLC5FkM85Nl9PCru888EQ70XwSCGSK74BZYRY1nWDxqcZ6ppdMT1D/jV/pOFwF
 dY0qN/vOJsj5OoYkwZHTd7ZL9/T4Qd4onb/lY7BZvN8qzVixZJhLhXNI5V/K0OraEM/4o/mKp
 LEs3lRjhC3u6lYn/6HOMmyrvnMZoU66axyig1tsWLO7LRjUuE6OQZGSgjq54BGlOF+Aiz2iyQ
 aN6kQsI6ZZElDb4NW+ZT4mc1s8PRi40OEXGoAOfK/g7YEpmid2CxE4O9hcEzLDOpEMeFVYchm
 au8PGDO8cTqYJ0okcUQGDNnIcg9NWVtaGLHMNSkFuVafu+EXJKrnNLkY9bxOnuxOfCsWiQ+Dm
 Bri01rIyYDpvyiKZbyTWb/8Bukk3bL27+IudftT5qHIh+EKNa4SkXBocPhU0wPtH3X0zHLrbu
 fSt+87LWeZUalx6Oy20oLpYCLr4G/x/H1T10G4eP2SeAJ3ULFdouSI+Q0aPrsy1My1B4VpeSj
 dCAk8NCFaTAOO88uMUpN7h1C0cH90NsxcFHVjz4AleWZGr4f7Z0wmKMTdpYSXj1Gc9UjAiuOy
 4LjwL0VM2ioMFqndISW/ccoo5cUdwh0ntESJRs5EQEXZaLQ6ZofBKxOInGyit6sN5nO2nMz+n
 g4/zzRprhseG46Yh7i+7vtXXdNmjpyIH3eDDbI34sz7qWrQOfRBxy3e6sMgmElCio0VVxp2Vm
 U+diz0OeBuU8MqLnxHn23GgcavDyC4CHeBYHReCIWjUfADl2brAB4l6EF7p7M6BGgtICDZetd
 ciNOpUH84HwBV49Dq7l+ps7qu8E=

Thanks for this very helpful information.
It is much better to understand than this ones:
https://www.kernel.org/doc/html/v4.11/process/submitting-patches.html
https://wireless.wiki.kernel.org/en/developers/Documentation/SubmittingPat=
ches

At the moment I still have no idea why the TP-Link TL-WN8200ND(UN) v3.0 so=
metimes work and
sometimes not (after its device idea has been added).
But I have seen this behavior (rtl8188eu), before:
https://bugzilla.kernel.org/show_bug.cgi?id=3D217205
Confirmed and fixed, now.

Maybe the problem of the rtl8192eu is similar to this - but I'm not sure, =
because
I haven't fully understood the entire driver code (relationship driver cod=
e and
firmware) yet.


Am 08.12.23 um 01:43 schrieb Ping-Ke Shih:
>
>
>> -----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@ke=
rnel.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 a=
nd
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingp=
atches
>
>
>