From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP2+: Remove legacy mailbox device instantiation
Date: Thu, 21 Jan 2016 13:57:45 -0800 [thread overview]
Message-ID: <20160121215744.GQ19432@atomide.com> (raw)
In-Reply-To: <56943936.4020003@ti.com>
* Suman Anna <s-anna@ti.com> [160111 15:23]:
> Hi Tony,
>
> On 10/22/2015 12:11 PM, Suman Anna wrote:
> > Hi Tony,
> >
> > On 09/14/2015 06:37 PM, Suman Anna wrote:
> >> The legacy-style mailbox device creation is supported currently
> >> only for OMAP3, as all other SoCs are DT-boot only. Even on this
> >> SoC, there are no client drivers that utilize these mailbox devices.
> >> So, clean up the legacy-style mailbox device instantiation logic.
> >> The mailbox devices are already present and supported for the DT
> >> boot on OMAP3.
> >>
> >> Signed-off-by: Suman Anna <s-anna@ti.com>
> >> ---
> >> arch/arm/mach-omap2/devices.c | 28 ----------------------------
> >> 1 file changed, 28 deletions(-)
> >>
> >
> > Ping, can you pick up this patch for your cleanup branch? FYI, Paul is
> > queueing Patch 2.
>
> Just checking your staged branches and linux-next, looks like this was
> missed. Let me know if you want me to repost this patch.
OK thanks applying into omap-for-v4.5/fixes.
Tony
next prev parent reply other threads:[~2016-01-21 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 23:37 [PATCH 0/2] Cleanup legacy OMAP mailbox support Suman Anna
2015-09-14 23:37 ` [PATCH 1/2] ARM: OMAP2+: Remove legacy mailbox device instantiation Suman Anna
2015-10-22 17:11 ` Suman Anna
2016-01-11 23:22 ` Suman Anna
2016-01-21 21:57 ` Tony Lindgren [this message]
2015-09-14 23:37 ` [PATCH 2/2] ARM: OMAP3: hwmod data: Remove legacy mailbox data and addrs Suman Anna
2015-10-22 16:44 ` Paul Walmsley
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=20160121215744.GQ19432@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).