From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Breno Leitao <leitao@debian.org>,
"leit@meta.com" <leit@meta.com>,
"open list:REALTEK WIRELESS DRIVER (rtw89)"
<linux-wireless@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH wireless] wifi: rtw89: Un-embed dummy device
Date: Thu, 09 May 2024 12:48:21 +0300 [thread overview]
Message-ID: <87o79fl3iy.fsf@kernel.org> (raw)
In-Reply-To: <acf2f82e7f424776835ffbc1f52ba996@realtek.com> (Ping-Ke Shih's message of "Thu, 9 May 2024 07:59:01 +0000")
Ping-Ke Shih <pkshih@realtek.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
next prev parent reply other threads:[~2024-05-09 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 18:23 [PATCH wireless] wifi: rtw89: Un-embed dummy device Breno Leitao
2024-04-25 5:52 ` Ping-Ke Shih
2024-04-25 5:57 ` Kalle Valo
2024-04-25 6:00 ` Kalle Valo
2024-04-25 6:15 ` Ping-Ke Shih
2024-05-09 7:48 ` Breno Leitao
2024-05-09 7:59 ` Ping-Ke Shih
2024-05-09 9:48 ` Kalle Valo [this message]
2024-05-09 11:03 ` Breno Leitao
2024-05-09 6:14 ` Ping-Ke Shih
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=87o79fl3iy.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=leit@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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