On Friday, February 27, 2015 03:23:13 PM Jonathan Corbet wrote:
> On Fri, 27 Feb 2015 23:41:05 +0100
> "Rafael J. Wysocki" wrote:
>
> > > Applied (with Peter's ack) to the docs tree.
> >
> > Well, I've applied it too in the meantime. :-)
> >
> > Also I'll have more commits on top of it, so it
On Fri, 27 Feb 2015 23:41:05 +0100
"Rafael J. Wysocki" wrote:
> > Applied (with Peter's ack) to the docs tree.
>
> Well, I've applied it too in the meantime. :-)
>
> Also I'll have more commits on top of it, so it's better if it goes through
> my tree I think, if you don't mind.
Gee, I feel
On Friday, February 27, 2015 03:08:10 PM Jonathan Corbet wrote:
> On Fri, 20 Feb 2015 14:53:46 +
> Mark Rutland wrote:
>
> > This patch updates the documentation regarding IRQF_NO_SUSPEND to make
> > this caveat explicit, hopefully making future misuse rarer. Cleanup of
> > existing misuse wi
On Fri, 20 Feb 2015 14:53:46 +
Mark Rutland wrote:
> This patch updates the documentation regarding IRQF_NO_SUSPEND to make
> this caveat explicit, hopefully making future misuse rarer. Cleanup of
> existing misuse will occur as part of later patch series.
Applied (with Peter's ack) to the d
On Tue, Feb 24, 2015 at 01:26:05AM +0100, Rafael J. Wysocki wrote:
> On Friday, February 20, 2015 02:53:46 PM Mark Rutland wrote:
> > The IRQF_NO_SUSPEND flag is intended to be used for interrupts required
> > to be enabled during the suspend-resume cycle. This mostly consists of
> > IPIs and timer
On Friday, February 20, 2015 02:53:46 PM Mark Rutland wrote:
> The IRQF_NO_SUSPEND flag is intended to be used for interrupts required
> to be enabled during the suspend-resume cycle. This mostly consists of
> IPIs and timer interrupts, potentially including chained irqchip
> interrupts if these ar
6 matches
Mail list logo