All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: Re: [GIT PULL V11] irq: next irq tracking
Date: Wed, 21 Jun 2017 12:57:18 +0200	[thread overview]
Message-ID: <20170621105718.GA2479@mai> (raw)
In-Reply-To: <alpine.DEB.2.20.1706210001280.2157@nanos>

On Wed, Jun 21, 2017 at 12:04:54AM +0200, Thomas Gleixner wrote:
> On Tue, 20 Jun 2017, Daniel Lezcano wrote:
> > The first patch adds the IRQF_TIMER flag to the timers which are percpu in
> > order to discard any timing measurement when the interrupt is coming from a
> > timer. All the timers changes have been discarded from V10.
> 
> I merily asked for splitting them out into a separate patch, but I'm fine
> with dropping them completely. But with them dropped, there is no point to
> actually change the interface right now. Then 1/3 can be dropped as well
> and we do a scripted interface change right before 4.13-rc1 and queue the
> timer driver changes for 4.14

Ok, I updated the irq timings branch without the 1/3.

 http://git.linaro.org/people/daniel.lezcano/linux.git next-irq/4.13-v11.1

-- 

 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2017-06-21 10:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 21:26 [GIT PULL V11] irq: next irq tracking Daniel Lezcano
2017-06-20 21:28 ` [PATCH 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Daniel Lezcano
2017-06-20 21:28   ` [PATCH 2/3] irq: Track the interrupt timings Daniel Lezcano
2017-06-22 14:47     ` Thomas Gleixner
2017-06-22 14:55       ` Daniel Lezcano
2017-06-20 21:28   ` [PATCH 3/3] irq: Compute the periodic interval for interrupts Daniel Lezcano
2017-06-22 15:25     ` Thomas Gleixner
2017-06-22 16:35       ` Daniel Lezcano
2017-06-22  9:31   ` [PATCH 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Mark Rutland
2017-06-22 10:36     ` Daniel Lezcano
2017-06-20 22:04 ` [GIT PULL V11] irq: next irq tracking Thomas Gleixner
2017-06-21 10:57   ` Daniel Lezcano [this message]
2017-07-06 12:29   ` [PATCH V11] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Daniel Lezcano
2017-07-06 21:21     ` [tip:irq/urgent] genirq: " tip-bot for Daniel Lezcano

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=20170621105718.GA2479@mai \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.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.