From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap generic wakeirq for v4.2 merge window
Date: Wed, 1 Jul 2015 23:10:12 -0700 [thread overview]
Message-ID: <20150702061011.GX4156@atomide.com> (raw)
In-Reply-To: <7hh9pnmxry.fsf@deeprootsystems.com>
* Kevin Hilman <khilman@kernel.org> [150701 13:26]:
> Tony Lindgren <tony@atomide.com> writes:
> >
> > This one is OK to merge now, both pm-wakeirq and tty-next
> > dependencies have been merged. This leaves the following
> > diffstat for thees changes:
>
> OK, thanks. I'm collecting a few remaining things for a "late" branch,
> but if I miss the merge window, I'll queue it up for -rc2.
OK thanks -rc cycle should be doable too as these fix issues with
interrupt re-entrancy that's possible if the wakeirq and the
device IO interrupt ever fire at the same time. So far have not
seen that though.. But that's mostly luck.
Regrads,
Tony
prev parent reply other threads:[~2015-07-02 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 11:46 [GIT PULL] omap generic wakeirq for v4.2 merge window Tony Lindgren
2015-06-29 6:04 ` Tony Lindgren
2015-07-01 20:24 ` Kevin Hilman
2015-07-02 6:10 ` Tony Lindgren [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=20150702061011.GX4156@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).