All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
	Cyril Hrubis <chrubis@suse.cz>, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/3] sched/rt fixes for 4.19
Date: Thu, 22 Feb 2024 18:19:27 +0100	[thread overview]
Message-ID: <2024022258-hypocrisy-unrigged-6905@gregkh> (raw)
In-Reply-To: <20240222165049.GA1373797@pevik>

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

      reply	other threads:[~2024-02-22 17:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 15:13 [PATCH 0/3] sched/rt fixes for 4.19 Petr Vorel
2024-02-22 15:13 ` [PATCH 1/3] sched/rt: Fix sysctl_sched_rr_timeslice intial value Petr Vorel
2024-02-22 15:13 ` [PATCH 2/3] sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset Petr Vorel
2024-02-22 15:13 ` [PATCH 3/3] sched/rt: Disallow writing invalid values to sched_rt_period_us Petr Vorel
2024-02-22 15:13 ` [PATCH 0/3] sched/rt fixes for 5.15, 5.10, 5.4 Petr Vorel
2024-02-22 15:36   ` Petr Vorel
2024-02-22 15:13 ` [PATCH 1/3] sched/rt: Fix sysctl_sched_rr_timeslice intial value Petr Vorel
2024-02-22 15:13 ` [PATCH 2/3] sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset Petr Vorel
2024-02-22 15:13 ` [PATCH 3/3] sched/rt: Disallow writing invalid values to sched_rt_period_us Petr Vorel
2024-02-22 15:13 ` [PATCH 0/2] sched/rt fixes for 6.1 Petr Vorel
2024-02-22 15:13 ` [PATCH 1/2] sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset Petr Vorel
2024-02-22 15:13 ` [PATCH 2/2] sched/rt: Disallow writing invalid values to sched_rt_period_us Petr Vorel
2024-02-22 15:13 ` [PATCH 0/1] sched/rt fixes for 6.6 Petr Vorel
2024-02-22 15:13 ` [PATCH 1/1] sched/rt: Disallow writing invalid values to sched_rt_period_us Petr Vorel
2024-02-22 15:32 ` [PATCH 0/3] sched/rt fixes for 4.19 Greg Kroah-Hartman
2024-02-22 16:50   ` Petr Vorel
2024-02-22 17:19     ` Greg Kroah-Hartman [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=2024022258-hypocrisy-unrigged-6905@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=chrubis@suse.cz \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pvorel@suse.cz \
    --cc=sashal@kernel.org \
    --cc=stable@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.