[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d2a50ca6452a13c94e94e839577b5914e96bacbb.camel@perches.com>
Date: Thu, 03 Mar 2022 21:40:45 -0800
From: Joe Perches <joe@...ches.com>
To: Bart Van Assche <bvanassche@....org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Finn Thain <fthain@...ux-m68k.org>
Cc: Konrad Wilhelm Kleine <kkleine@...hat.com>,
Tom Rix <trix@...hat.com>, kashyap.desai@...adcom.com,
sumit.saxena@...adcom.com, shivasharan.srikanteshwara@...adcom.com,
jejb@...ux.ibm.com, martin.petersen@...cle.com,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
megaraidlinux.pdl@...adcom.com, scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>, llvm@...ts.linux.dev
Subject: Re: [PATCH] scsi: megaraid: cleanup formatting of megaraid
On Thu, 2022-03-03 at 21:22 -0800, Bart Van Assche wrote:
> On 3/3/22 15:38, Joe Perches wrote:
> > One argument is that churn leads to difficulty in backporting
> > fixes to older 'stable' versions.
> >
> > I think the churn argument is overstated.
>
> I'm often backporting patches to older kernels and I think the churn argument
> has not been emphasized enough. Backporting patches is a normal aspect of a
> product lifecycle since a kernel version is chosen when development of a
> product starts and bugfixes are cherry-picked from upstream selectively.
Stable backporting is almost certainly what people get _paid_ to do.
IMO the most important tree is the current one not backports to stable.
Powered by blists - more mailing lists