From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: "Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH v10 0/1] wfx: get out from the staging area
Date: Tue, 5 Apr 2022 09:20:46 -0700 [thread overview]
Message-ID: <20220405092046.465ff7e5@kernel.org> (raw)
In-Reply-To: <878rskrod1.fsf@kernel.org>
On Tue, 05 Apr 2022 10:16:58 +0300 Kalle Valo wrote:
> Sure, that would technically work. But I just think it's cleaner to use
> -rc1 (or later) as the baseline for an immutable branch. If the baseline
> is an arbitrary commit somewhere within merge windows commits, it's more
> work for everyone to verify the branch is suitable.
>
> Also in general I would also prefer to base -next trees to -rc1 or newer
> to make the bisect cleaner. The less we need to test kernels from the
> merge window (ie. commits after the final release and before -rc1) the
> better.
>
> But this is just a small wish from me, I fully understand that it might
> be too much changes to your process. Wanted to point out this anyway.
Forwarded!
next prev parent reply other threads:[~2022-04-06 3:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 9:21 [PATCH v10 0/1] wfx: get out from the staging area Jerome Pouiller
2022-02-26 9:21 ` [PATCH v10 1/1] " Jerome Pouiller
2022-02-26 10:41 ` [PATCH v10 0/1] " Kalle Valo
2022-02-26 12:56 ` Greg Kroah-Hartman
2022-02-26 13:15 ` Kalle Valo
2022-04-04 9:31 ` Jérôme Pouiller
2022-04-04 10:49 ` Kalle Valo
2022-04-05 6:22 ` Jakub Kicinski
2022-04-05 6:29 ` Jakub Kicinski
2022-04-05 7:16 ` Kalle Valo
2022-04-05 16:20 ` Jakub Kicinski [this message]
2022-04-06 7:06 ` Kalle Valo
2022-04-07 17:42 ` Greg Kroah-Hartman
2022-04-12 14:42 ` Kalle Valo
2022-02-28 16:00 ` Jérôme Pouiller
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=20220405092046.465ff7e5@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jerome.pouiller@silabs.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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.