diff options
Diffstat (limited to '')
| -rw-r--r-- | debian/patches-rt/0017-printk-nbcon-Ensure-ownership-release-on-failed-emit.patch (renamed from debian/patches-rt/0101-printk-nbcon-Ensure-ownership-release-on-failed-emit.patch) | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/debian/patches-rt/0101-printk-nbcon-Ensure-ownership-release-on-failed-emit.patch b/debian/patches-rt/0017-printk-nbcon-Ensure-ownership-release-on-failed-emit.patch index d96f2dc2b9..65553848f5 100644 --- a/debian/patches-rt/0101-printk-nbcon-Ensure-ownership-release-on-failed-emit.patch +++ b/debian/patches-rt/0017-printk-nbcon-Ensure-ownership-release-on-failed-emit.patch @@ -1,8 +1,7 @@ From: John Ogness <john.ogness@linutronix.de> Date: Fri, 20 Oct 2023 09:52:59 +0000 -Subject: [PATCH 101/134] printk: nbcon: Ensure ownership release on failed - emit -Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/6.6/older/patches-6.6.7-rt18.tar.xz +Subject: [PATCH 17/50] printk: nbcon: Ensure ownership release on failed emit +Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/6.7/older/patches-6.7-rt6.tar.xz Until now it was assumed that ownership has been lost when the write_atomic() callback fails. nbcon_emit_next_record() only |