linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: some clock/hwmod patches for v3.19
Date: Fri, 14 Nov 2014 10:47:20 -0800	[thread overview]
Message-ID: <20141114184719.GA7046@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1411132249550.17030@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [141113 14:52]:
> The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
> 
>   Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v3.19/omap-a
> 
> for you to fetch changes up to 79005fbd3e1d671d08c45c9140ee9826efdc367c:
> 
>   ARM: OMAP2+: hwmod: drop unnecessary list initialization (2014-11-13 09:36:55 -0700)
> 
> ----------------------------------------------------------------
> Some OMAP clock/hwmod patches for v3.19.
> 
> Most of the patches are clock-related.  The DPLL implementation is
> changed to better align to the common clock framework.
> There is also a patch that removes a few lines from the hwmod code -
> this patch should have no functional effect.
> 
> Basic build, boot, and PM test logs for these patches can be found here:
> 
> http://www.pwsan.com/omap/testlogs/omap-a-for-v3.19/20141113094101/

Pulling into omap-for-v3.19/soc thanks. FYI, looks like there are
few more open hwmod related threads you may want to look at:

[PATCH v2 0/3] Add support for ADC on am437x-gp and am43x-epos-evm
[RFC PATCH 0/6] ARM: OMAP4+: hwmod: fixing omap4+ DSS hwmods
[PATCH] ARM: DRA7: hwmod data: Add missing UART hwmod data

Regards,

Tony

  reply	other threads:[~2014-11-14 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 22:50 [GIT PULL] ARM: OMAP2+: some clock/hwmod patches for v3.19 Paul Walmsley
2014-11-14 18:47 ` Tony Lindgren [this message]
2014-11-20 17:29   ` 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=20141114184719.GA7046@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).