linux-kernel - Re: [PATCH wireless] wifi: rtw89: Un-embed dummy device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87o79fl3iy.fsf@kernel.org>
Date: Thu, 09 May 2024 12:48:21 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Ping-Ke Shih <pkshih@...ltek.com>
Cc: Breno Leitao <leitao@...ian.org>,  "leit@...a.com" <leit@...a.com>,
  "open list:REALTEK WIRELESS DRIVER (rtw89)"
 <linux-wireless@...r.kernel.org>,  "open list"
 <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH wireless] wifi: rtw89: Un-embed dummy device

Ping-Ke Shih <pkshih@...ltek.com> writes:

>> Out of curiosity, why don't you rebase your tree to net-next/linux-next
>> frequently?
>
> My tree goes to wireless-next, so I think it should be always based on
> wireless-next. Once wirelss-next rebase (ff-merge) net-next, my tree will
> have them also. 

The simple answer about updating to net-next frequently: it's
complicated :)

The long answer is that the guidance from Linus is to avoid making
unnecessary merges so we fast forward wireless-next only after it's
pulled to net-next. And we can't rebase wireless-next due to downstream
trees Ping's rtw tree, besides rebasing public git trees is evil anyway.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches