From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mark Gross <markgross@kernel.org>
Cc: linux-rt-users@vger.kernel.org, stable-rt@vger.kernel.org,
Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: [PATCH 0/9 v4.9-RT] Backports to fix random core
Date: Fri, 2 Sep 2022 08:52:18 +0200 [thread overview]
Message-ID: <YxGoItZaDcwxRcV5@linutronix.de> (raw)
In-Reply-To: <YxEhJqm40AIPxCTX@T470>
On 2022-09-01 14:16:22 [-0700], Mark Gross wrote:
> Sorry for taking so long to start working these. Are these patches to be
> applied to v4.9.320, or to the RT patches prior to the linux-stable merge?
>
> Or are these patches the updates to the patches that conflict with v4.9.320 as
> I rebase?
>
> I'm guessing the latter as the patches don't seem to work on just the last RT
> release or v4.9.320 directly.
>
> Bottom line, I'm not sure how you expected me to use these 9 patches.
The commit I cited was backported into v4.9-stable, I *think* it is part
of v4.9-stable as of v4.9.320. If you apply the RT queue then you should
have conflicts. The "old" RT patches for random are obsolete if I
remember correctly.
> Sorry for being dense.
No worries. If in doubt, make a -rc and let me look over it or if
completely in doubt yell and I prepare a complete queue.
> --mark
Sebastian
prev parent reply other threads:[~2022-09-02 6:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 9:24 [PATCH 0/9 v4.9-RT] Backports to fix random core Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 1/9] random: Bring back the local_locks Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 2/9] random: schedule mix_interrupt_randomness() less often Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 3/9] Revert "workqueue: Use local irq lock instead of irq disable regions" Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 4/9] Revert "workqueue: Prevent deadlock/stall on RT" Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 5/9] timers: Keep interrupts disabled for TIMER_IRQSAFE timer Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 6/9] timers: Don't block on ->expiry_lock for TIMER_IRQSAFE timers Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 7/9] rcu: Intrdroduce rcuwait Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 8/9] workqueue: Use rcuwait for wq_manager_wait Sebastian Andrzej Siewior
2022-08-19 9:24 ` [PATCH 9/9] workqueue: Convert the pool::lock and wq_mayday_lock to raw_spinlock_t Sebastian Andrzej Siewior
2022-08-19 15:14 ` [PATCH 0/9 v4.9-RT] Backports to fix random core Mark Gross
2022-09-01 21:16 ` Mark Gross
2022-09-02 6:52 ` Sebastian Andrzej Siewior [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=YxGoItZaDcwxRcV5@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=carnil@debian.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=stable-rt@vger.kernel.org \
/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.