From: Michael Schmitz <schmitzmic@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
linux-m68k@vger.kernel.org
Cc: geert@linux-m68k.org, uli@fpond.eu, fthain@linux-m68k.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH v3 0/8] m68k v4.4 backport fixes
Date: Wed, 7 Feb 2024 10:37:08 +1300 [thread overview]
Message-ID: <1ec6b945-4eba-4cf6-8ca5-3db88b7f92de@gmail.com> (raw)
In-Reply-To: <1ff0280f69c02b4e64e1a1055c9411ecbff9ffc0.camel@physik.fu-berlin.de>
Hi Adrian,
On 7/02/24 10:15, John Paul Adrian Glaubitz wrote:
> Hi Michael,
>
> On Wed, 2024-02-07 at 10:10 +1300, Michael Schmitz wrote:
>> IP v4.4 backport patches for m68k. Basically everything needed
>> to make v4.4 work on my Falcon. This includes my iounmap() fix,
>> Al Viro's signal handling and uaccess page fault fixes, my 030
>> buserr_c fix for exception handling during page faults, and Finn's
>> 030 signal frame fix.
> Correct me if I'm wrong, but 4.4 is no longer maintained, is it?
>
> It seems that the last LTS release for 4.4 was 4.4.302 [1].
That is correct. You will note that none of my patches did contain a Cc:
stable@vger.kernel.org tag.
This is about CIP releases - see
https://wiki.linuxfoundation.org/civilinfrastructureplatform/start for
more information. EOL for the CIP 4.4 kernel is projected to be 01/2027.
That's still some way off.
Cheers,
Michael
>
> Adrian
>
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tag/?h=v4.4.302
prev parent reply other threads:[~2024-02-06 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 21:10 [PATCH v3 0/8] m68k v4.4 backport fixes Michael Schmitz
2024-02-06 21:10 ` [PATCH v3 1/8] m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap() Michael Schmitz
2024-02-06 21:10 ` [PATCH v3 2/8] m68k: Only force 030 bus error if PC not in exception table Michael Schmitz
2024-02-06 21:10 ` [PATCH v3 3/8] m68k: include module.h to make use of exception handling in traps.c Michael Schmitz
2024-02-06 21:11 ` [PATCH v3 4/8] m68k: Handle arrivals of multiple signals correctly Michael Schmitz
2024-02-06 21:11 ` [PATCH v3 5/8] m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal Michael Schmitz
2024-02-06 21:11 ` [PATCH v3 6/8] m68k: Leave stack mangling to asm wrapper of sigreturn() Michael Schmitz
2024-02-06 21:11 ` [PATCH v3 7/8] m68k: fix livelock in uaccess Michael Schmitz
2024-02-06 21:11 ` [PATCH v3 8/8] m68k: Move signal frame following exception on 68020/030 Michael Schmitz
2024-02-06 21:15 ` [PATCH v3 0/8] m68k v4.4 backport fixes John Paul Adrian Glaubitz
2024-02-06 21:37 ` Michael Schmitz [this message]
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=1ec6b945-4eba-4cf6-8ca5-3db88b7f92de@gmail.com \
--to=schmitzmic@gmail.com \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=uli@fpond.eu \
--cc=viro@zeniv.linux.org.uk \
/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.