From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] OMAP: AM3xxx: cpu_is dead code removal
Date: Mon, 4 Jun 2012 03:31:07 -0700 [thread overview]
Message-ID: <20120604103106.GA12766@atomide.com> (raw)
In-Reply-To: <877gvt44mv.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120530 16:47]:
> Tony,
>
> These couple patches didn't make it for v3.5 because of some cross-tree
> dependencies. All the dependencies are now merged (after Linus merged
> arm-soc/next/pm), so here's the remaining patches.
>
> Not sure if you want to get them in for 3.5-rc or queue them in your
> cleanup branch for v3.6. Up to you.
Pulled into fixes, this should be OK for -rc1.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP: AM3xxx: cpu_is dead code removal
Date: Mon, 4 Jun 2012 03:31:07 -0700 [thread overview]
Message-ID: <20120604103106.GA12766@atomide.com> (raw)
In-Reply-To: <877gvt44mv.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120530 16:47]:
> Tony,
>
> These couple patches didn't make it for v3.5 because of some cross-tree
> dependencies. All the dependencies are now merged (after Linus merged
> arm-soc/next/pm), so here's the remaining patches.
>
> Not sure if you want to get them in for 3.5-rc or queue them in your
> cleanup branch for v3.6. Up to you.
Pulled into fixes, this should be OK for -rc1.
Regards,
Tony
next prev parent reply other threads:[~2012-06-04 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 23:43 [GIT PULL] OMAP: AM3xxx: cpu_is dead code removal Kevin Hilman
2012-05-30 23:43 ` Kevin Hilman
2012-06-04 10:31 ` Tony Lindgren [this message]
2012-06-04 10:31 ` 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=20120604103106.GA12766@atomide.com \
--to=tony@atomide.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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.