From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: some hwmod data patches for v3.16
Date: Fri, 16 May 2014 14:23:27 -0700 [thread overview]
Message-ID: <20140516212327.GI12881@atomide.com> (raw)
In-Reply-To: <5375CE74.6000603@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [140516 01:39]:
> Hi Paul,
>
> On 16/05/14 07:45, Paul Walmsley wrote:
> > Hi Tony
> >
> > The following changes since commit d1db0eea852497762cab43b905b879dfcd3b8987:
> >
> > Linux 3.15-rc3 (2014-04-27 19:29:27 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git for-v3.16/hwmod-a
> >
> > for you to fetch changes up to 433480707967187a74ced38bd38edba749998013:
> >
> > ARM: OMAP2+: hwmod: OMAP5 DSS hwmod data (2014-05-14 12:26:10 -0600)
> >
> > ----------------------------------------------------------------
> > First (and possibly last) set of hwmod data changes for v3.16. This
> > set should clean up some obsolete OMAP4 hwmod data, and add OMAP5 DSS
> > support.
>
> What about the AM43xx hwmod data I sent in the same series:
>
> http://article.gmane.org/gmane.linux.ports.arm.omap/114192
I guess the issue there is that there's no way for Paul or much
anybody else to check it against any documentation or hardware :(
Is this just cut and paste code, or has you verified it against
the documentation and the hardare?
Anyways, pulling this set into omap-for-v3.16/soc thanks.
Regards,
Tony
next prev parent reply other threads:[~2014-05-16 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 4:45 [GIT PULL] ARM: OMAP2+: some hwmod data patches for v3.16 Paul Walmsley
2014-05-16 8:38 ` Tomi Valkeinen
2014-05-16 21:23 ` Tony Lindgren [this message]
2014-05-19 9:01 ` Tomi Valkeinen
2014-05-19 16:09 ` 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=20140516212327.GI12881@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).