All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xuewei Zhang <xueweiz@google.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: Request to backport 4929a4e6faa0 to stable tree
Date: Sat, 7 Dec 2019 11:35:44 -0800	[thread overview]
Message-ID: <CAPtwhKpi2OX4D1w3ncnnQV5fNeTfnhYcYN0YghLhpXPYWePbyg@mail.gmail.com> (raw)
In-Reply-To: <20191207115754.GB325082@kroah.com>

On Sat, Dec 7, 2019 at 3:57 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Fri, Dec 06, 2019 at 05:47:10PM -0800, Xuewei Zhang wrote:
> > On Fri, Dec 6, 2019 at 6:11 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > 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?
> >
> > Yes, sorry it's by accident.
> >
> > >
> > > 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 :(
> >
> > Sorry for the formatting problem Greg.
> >
> > I just used `git send-email` to sent out the backports. They are at:
> > v4.19: https://www.spinics.net/lists/stable/msg347573.html
> > v4.14: https://www.spinics.net/lists/stable/msg347576.html
> > v4.9: https://www.spinics.net/lists/stable/msg347577.html
> > v4.4: https://www.spinics.net/lists/stable/msg347578.html
> > v3.16: https://www.spinics.net/lists/stable/msg347579.html
> >
> > Hopefully that could work for you. But if they are still broken somehow
> > (for which I'd be very sorry), you could consider cherry-picking the patch
> > from my Github repository (forked from yours):
>
> Those worked just fine from the emails you just sent (note, try using
> lore.kernel.org instead of other mail archives, as I could not pull a
> patch out of spinics.net).
>
> I'll let Ben take the 3.16 version, as he handles that tree.
>
> thanks,
>
> greg k-h

Thanks a lot Greg!

I will use lore.kernel.org next time. Thanks for the tips!

Best regards,
Xuewei

      reply	other threads:[~2019-12-07 19:35 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
2019-12-07  1:47         ` Xuewei Zhang
2019-12-07 11:57           ` Greg KH
2019-12-07 19:35             ` Xuewei Zhang [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=CAPtwhKpi2OX4D1w3ncnnQV5fNeTfnhYcYN0YghLhpXPYWePbyg@mail.gmail.com \
    --to=xueweiz@google.com \
    --cc=gregkh@linuxfoundation.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.