diff options
Diffstat (limited to '')
| -rw-r--r-- | debian/patches-rt/0011-printk-ringbuffer-Consider-committed-as-finalized-in.patch (renamed from debian/patches-rt/0095-printk-ringbuffer-Consider-committed-as-finalized-in.patch) | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/debian/patches-rt/0095-printk-ringbuffer-Consider-committed-as-finalized-in.patch b/debian/patches-rt/0011-printk-ringbuffer-Consider-committed-as-finalized-in.patch index 932ba13e7d..405969873c 100644 --- a/debian/patches-rt/0095-printk-ringbuffer-Consider-committed-as-finalized-in.patch +++ b/debian/patches-rt/0011-printk-ringbuffer-Consider-committed-as-finalized-in.patch @@ -1,8 +1,8 @@ From: John Ogness <john.ogness@linutronix.de> Date: Mon, 20 Nov 2023 12:46:35 +0100 -Subject: [PATCH 095/134] printk: ringbuffer: Consider committed as finalized - in panic -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/6.6/older/patches-6.6.7-rt18.tar.xz +Subject: [PATCH 11/50] printk: ringbuffer: Consider committed as finalized in + panic +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/6.7/older/patches-6.7-rt6.tar.xz A descriptor in the committed state means the record does not yet exist for the reader. However, for the panic CPU, committed |