From: Kevin Hilman <khilman@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] omap generic wakeirq for v4.2 merge window
Date: Wed, 01 Jul 2015 13:24:33 -0700 [thread overview]
Message-ID: <7hh9pnmxry.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150629060409.GQ4156@atomide.com> (Tony Lindgren's message of "Sun, 28 Jun 2015 23:04:09 -0700")
Tony Lindgren <tony@atomide.com> writes:
> Hi,
>
> * Tony Lindgren <tony@atomide.com> [150616 04:48]:
>> Hi,
>>
>> Here's a late pull request that would be good to get into v4.2.
>> This series mostly just drops code that's now unnecessary, and
>> also fixes potential interrupt re-entrancy issues that the old
>> handling has.
>>
>> The series changes omap hsmmc, 8250_omap and omap-serial to use
>> the Linux generic wakeirq. I had to redo the branch last week on
>> recent tty-next branch because of a merge conflict. Other than
>> that, these patches were already in Linux next earlier.
>>
>> The pull request below also shows the related patches in Rafael's
>> pm-wakeirq branch as I did not create a separate merge commit to
>> base patches on.
>>
>> This branch depends on both Rafael's pm-wakeirq and Greg's
>> tty-next, so it should be sent separately towards the end of the
>> merge window.
>
> 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.
Kevin
next prev parent reply other threads:[~2015-07-01 20:24 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 [this message]
2015-07-02 6:10 ` Tony Lindgren
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=7hh9pnmxry.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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).