linux-kernel - Re: [PATCH] Documentation: describe how to apply incremental stable patches

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: <YilGgO03v+CM0aDq@llamedos.localdomain>
Date:   Thu, 10 Mar 2022 00:29:52 +0000
From:   Ken Moffat <zarniwhoop@...world.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Bagas Sanjaya <bagasdotme@...il.com>, linux-doc@...r.kernel.org,
        SeongJae Park <sjpark@...zon.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: describe how to apply incremental stable
 patches

On Wed, Mar 09, 2022 at 04:29:28PM -0700, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@...il.com> writes:
> 
> > The applying patches document
> > (Documentation/process/applying-patches.rst) mentions incremental stable
> > patches, but there is no example of how to apply them. Describe the
> > process.
> >
> > While at it, remove note about incremental patches and move the external
> > link of 5.x.y incremental patches to "Where can I download patches?"
> > section.
> >
> > Cc: Jonathan Corbet <corbet@....net>
> > Cc: SeongJae Park <sjpark@...zon.de>
> > Cc: linux-kernel@...r.kernel.org
> > Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
> > ---
> >  Documentation/process/applying-patches.rst | 28 ++++++++++++++++++----
> >  1 file changed, 23 insertions(+), 5 deletions(-)
> 
> I've applied this, thanks.  I do have to wonder, though, how useful this
> information is anymore.  Does anybody actually apply kernel-patch files
> this far into the Git era?
> 
> Thanks,
> 
> jon

I do.  I have several machines with multiple systems (current, old,
older, experimental) and mostly I build current kernels in the
current system, and older LTS in the old systems.  Ideally I will
find time to test an rc, but I only use git for kernels when I need
to bisect.  I find it much easier to keep the initial relase tarball
and chosen point patches on my local nfs.

My interests are userspace, and some of my machines are
comparatively slow to compile kernels.

ĸen 

-- 
The beauty of reading a page of de Selby is that it leads one
inescapably to the conclusion that one is not, of all nincompoops,
the greatest.            -- du Garbandier