All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xuewei Zhang <xueweiz@google.com>
Cc: stable@vger.kernel.org
Subject: Re: Request to backport 4929a4e6faa0 to stable tree
Date: Fri, 6 Dec 2019 15:11:29 +0100	[thread overview]
Message-ID: <20191206141129.GA9376@kroah.com> (raw)
In-Reply-To: <CAPtwhKqiKZtTGO_7Jpx9nEDhQu8LESvaZth4uHb5a8Ur+=65SA@mail.gmail.com>

On Tue, Dec 03, 2019 at 03:30:05PM -0800, Xuewei Zhang wrote:
> Backport patch that cleanly applies for 4.19, 4.14, 4.9, 4.4 stable trees:

Did you send this twice?

And the patch is totally corrupted:

> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index f77fcd37b226..f0abb8fe0ae9 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -4868,20 +4868,28 @@ static enum hrtimer_restart
> sched_cfs_period_timer(struct hrtimer *timer)
>   if (++count > 3) {
>   u64 new, old = ktime_to_ns(cfs_b->period);
> 
> - new = (old * 147) / 128; /* ~115% */
> - new = min(new, max_cfs_quota_period);
> -
> - cfs_b->period = ns_to_ktime(new);
> -

All of your leading whitespace is gone.

You can't use the web client of gmail to send patches inline, sorry.

Can you fix this up and resend all of the backports, none of these
worked :(

greg k-h

  parent reply	other threads:[~2019-12-06 14:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 22:54 Request to backport 4929a4e6faa0 to stable tree Xuewei Zhang
2019-12-03 23:09 ` Greg KH
2019-12-03 23:17   ` Xuewei Zhang
2019-12-03 23:30     ` Xuewei Zhang
2019-12-03 23:30       ` Xuewei Zhang
2019-12-03 23:32         ` Xuewei Zhang
2019-12-03 23:37           ` Xuewei Zhang
2019-12-04  7:11             ` Greg KH
2019-12-04  7:14               ` Xuewei Zhang
2019-12-06 14:11       ` Greg KH [this message]
2019-12-07  1:47         ` Xuewei Zhang
2019-12-07 11:57           ` Greg KH
2019-12-07 19:35             ` Xuewei Zhang

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=20191206141129.GA9376@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=xueweiz@google.com \
    /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.