From: Conor Dooley <conor@kernel.org>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Emil Renner Berthing" <kernel@esmil.dk>,
"Samuel Holland" <samuel.holland@sifive.com>,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-riscv@lists.infradead.org,
"Andy Chiu" <andy.chiu@sifive.com>,
"Jakub Kicinski" <kuba@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: RISC-V for-next/fixes (cont'd from PW sync)
Date: Wed, 27 Mar 2024 20:32:33 +0000 [thread overview]
Message-ID: <20240327-irrigate-unread-d9de28174437@spud> (raw)
In-Reply-To: <87ttkro3b5.fsf@all.your.base.are.belong.to.us>
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
On Wed, Mar 27, 2024 at 08:57:50PM +0100, Björn Töpel wrote:
> Hi,
>
> I figured I'd put some words on the "how to update the RISC-V
> for-next/fixes branches [1]" that came up on the patchwork call today.
>
> In RISC-V land, the for-next branch is used for features, and typically
> sent as a couple of PRs to Linus when the merge window is open. The
> fixes branch is sent as PR(s) between the RCs of a release.
>
> Today, the baseline for for-next/fixes is the CURRENT_RELEASE-rc1, and
> features/fixes are based on that.
>
> This has IMO a couple of issues:
>
> 1. fixes is missing the non-RISC-V fixes from releases later than
> -rc1, which makes it harder for contributors.
> 2. for-next does not have the fixes from RISC-V/rest of the kernel,
> and it's hard for contributors to test the work on for-next (buggy,
> no fixes, and sometime missing deps).
>
> I used to spend a whole lot of mine time in the netdev tree of the
> kernel, and this is how they manage it (Thanks Kuba!):
>
> Netdev (here exchanged to RISC-V trees), fast-forward fixes, and then
> cross-merge fixes into for-next -- for every -rc.
>
> E.g., say fixes is submitted for -rc2 to Linus, once he pulls, do:
>
> git push --delete origin $SOMETAG
> git tag -d $SOMETAG
> git pull --ff-only --tags git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> build / test / push out.
>
> Then pull fixes into for-next:
>
> git pull --tags git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
>
>
> Personally (obviously biased), I think this would be easier for
> contributors. Any downsides from a RISC-V perspective?
After you left, Palmer said he'd go for merging his fixes tag into
for-next after they got merged by Linus. At least I think it was that,
rather than Linus' -rcs...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-27 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 19:57 RISC-V for-next/fixes (cont'd from PW sync) Björn Töpel
2024-03-27 20:32 ` Conor Dooley [this message]
2024-03-29 6:46 ` Alexandre Ghiti
2024-03-29 7:27 ` Conor Dooley
2024-03-29 9:10 ` Björn Töpel
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=20240327-irrigate-unread-d9de28174437@spud \
--to=conor@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=kernel@esmil.dk \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.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