All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ivan Delalande <colona@arista.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Rabin Vincent <rabin.vincent@axis.com>,
	Edward Chron <echron@arista.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 4.9 0/4] Fix softirq time accounting issues on 4.9
Date: Fri, 14 Sep 2018 08:57:48 +0200	[thread overview]
Message-ID: <20180914065748.GA3984@kroah.com> (raw)
In-Reply-To: <20180913231317.GB11928@visor>

On Thu, Sep 13, 2018 at 04:13:17PM -0700, Ivan Delalande wrote:
> Hey Greg,
> 
> Did you get a chance to look at this series? Thanks a lot!

Not yet, sorry, I was digging myself out from under the patch backlog of
all of the other stuff sent before this series.

It isn't lost, don't worry, give it a chance.  It's also almost a 2 year
old kernel you are using here, so there can't be a lot of rush :)

thanks,

greg k-h

  reply	other threads:[~2018-09-14 12:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07  1:42 [PATCH 4.9 0/4] Fix softirq time accounting issues on 4.9 Ivan Delalande
2018-09-07  1:42 ` [PATCH 4.9 1/4] time: Introduce jiffies64_to_nsecs() Ivan Delalande
2018-09-07  1:42 ` [PATCH 4.9 2/4] sched/cputime: Convert kcpustat to nsecs Ivan Delalande
2018-10-12 14:42   ` Greg Kroah-Hartman
2018-09-07  1:42 ` [PATCH 4.9 3/4] sched/cputime: Increment kcpustat directly on irqtime account Ivan Delalande
2018-09-07  1:42 ` [PATCH 4.9 4/4] sched/cputime: Fix ksoftirqd cputime accounting regression Ivan Delalande
2018-09-13 23:13 ` [PATCH 4.9 0/4] Fix softirq time accounting issues on 4.9 Ivan Delalande
2018-09-14  6:57   ` Greg Kroah-Hartman [this message]
2018-10-11 14:11     ` Greg Kroah-Hartman

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=20180914065748.GA3984@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=colona@arista.com \
    --cc=echron@arista.com \
    --cc=fweisbec@gmail.com \
    --cc=mingo@kernel.org \
    --cc=rabin.vincent@axis.com \
    --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.