From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
Cc: Linux OMAP List
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
"Krishnamoorthy,
Balaji T" <balajitk-l0cyMroinI0@public.gmane.org>,
Devicetree Discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Linux MMC List
<linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Joel A Fernandes
<agnel.joel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Chris Ball <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>,
Linux ARM Kernel List
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH 2/2] ARM: dts: add AM33XX MMC support
Date: Sun, 16 Jun 2013 23:20:53 -0700 [thread overview]
Message-ID: <20130617062052.GG20992@atomide.com> (raw)
In-Reply-To: <20130615150500.GA27629-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
* Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org> [130615 08:12]:
>
> fair enough, then let's just add those interrupts to hwmod which will,
> eventually, let us drop all of that data from hwmod.
Nope, we're already dropping the duplicate data from hwmod for
am33xx and omap4. See omap-for-v3.11/cleanup branch.
Regards,
Tony
prev parent reply other threads:[~2013-06-17 6:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 4:16 [PATCH 0/2] AM33xx mmc support Matt Porter
[not found] ` <1362629799-22485-1-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2013-03-07 4:16 ` [PATCH 1/2] mmc: omap_hsmmc: set max_segs based on dma engine limits Matt Porter
2013-03-07 4:16 ` [PATCH 2/2] ARM: dts: add AM33XX MMC support Matt Porter
[not found] ` <1362629799-22485-3-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2013-03-07 5:29 ` Hiremath, Vaibhav
[not found] ` <41fde401c8e646689123d7c6d3a2dffc@DLEE71.ent.ti.com>
2013-03-07 14:12 ` Matt Porter
2013-03-07 14:39 ` Hiremath, Vaibhav
2013-03-07 14:46 ` Matt Porter
2013-03-07 14:51 ` Matt Porter
2013-03-07 14:53 ` Hiremath, Vaibhav
2013-03-07 15:00 ` Matt Porter
2013-03-07 15:03 ` Hiremath, Vaibhav
2013-03-07 14:59 ` Hiremath, Vaibhav
2013-03-07 15:04 ` Matt Porter
2013-03-07 15:50 ` Hiremath, Vaibhav
2013-03-07 16:02 ` Matt Porter
2013-03-08 12:29 ` Hiremath, Vaibhav
2013-06-14 19:54 ` Joel A Fernandes
2013-06-14 22:26 ` Felipe Balbi
[not found] ` <20130614222537.GA25428-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-06-14 23:43 ` Joel A Fernandes
[not found] ` <CAD=GYpYfMAZeV1RUC=DqhYGZaKiiukpTZg7bhO582eKwimS9aA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-15 7:23 ` Joel A Fernandes
2013-06-15 15:05 ` Felipe Balbi
[not found] ` <20130615150500.GA27629-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-06-17 6:20 ` 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=20130617062052.GG20992@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=agnel.joel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=balajitk-l0cyMroinI0@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).