On Thu, Feb 22, 2024 at 05:50:49PM +0100, Petr Vorel wrote: > Hi Greg, > > > On Thu, Feb 22, 2024 at 04:13:21PM +0100, Petr Vorel wrote: > > > Hi, > > > > maybe you will not like introducing 'static int int_max = INT_MAX;' for > > > this old kernel which EOL in 10 months. > > > That's fine, not a big deal :) > > Thanks for a quick info. I guess this is a reply to my question about > SYSCTL_NEG_ONE failure on missing SYSCTL_NEG_ONE. Therefore I'll create > static int __maybe_unused neg_one = -1; (which was used before 78e36f3b0dae). Great. > > > Cyril Hrubis (3): > > > sched/rt: Fix sysctl_sched_rr_timeslice intial value > > > sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset > > > sched/rt: Disallow writing invalid values to sched_rt_period_us > > > > kernel/sched/rt.c | 10 +++++----- > > > kernel/sysctl.c | 5 +++++ > > > 2 files changed, 10 insertions(+), 5 deletions(-) > > > Thanks for the patches, but they all got connected into the same thread, > > making it impossible to detect which ones are for what branches :( > > > Can you put the version in the [PATCH X/Y] section like [PATCH 4.14 X/Y] > > or just make separate threads so we have a chance? > > I'm sorry, I'll resent all patches properly. No worries, the second round looks good. I'll queue them up after this latest set of stable kernels goes out in a few days. thanks! greg k-h
