All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] ARM: OMAP AM35xx: some fixes for 3.6 (fwd)
Date: Thu, 28 Jun 2012 05:12:38 -0700	[thread overview]
Message-ID: <20120628121238.GF19842@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206280220240.2338@utopia.booyaka.com>

Hi,

* Paul Walmsley <paul@pwsan.com> [120628 01:25]:
> 
> The following changes since commit 6b16351acbd415e66ba16bf7d473ece1574cf0bc:
> 
>   Linux 3.5-rc4 (2012-06-24 12:53:04 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git 
> 
> for you to fetch changes up to a77e1c4d09c88f98ac2e653382d2c1861dbb736f:
> 
>   Merge branches 'am35xx_hwmod_data_fixes_a_3.6', 'am35xx_emac_mdio_devel_3.6' and 'am35xx_prcm_data_devel_3.6' into am35xx_devel_3.6 (2012-06-28 00:13:19 -0600)
> 
> ----------------------------------------------------------------
> 
> Some OMAP AM35xx fixes.
> 
> The powerdomain and clockdomain data for the AM35xx are finally fixed.
> The AM35xx EMAC/MDIO Ethernet controller integration code has been
> converted to use the OMAP device and hwmod framework.  Also the UART4
> and HSOTGUSB warnings have been fixed.
> 
> ----------------------------------------------------------------

Looks like the tag name or git branch to pull is missing above?
There's just the git tree.

Tony

  reply	other threads:[~2012-06-28 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  8:20 [GIT PULL] ARM: OMAP AM35xx: some fixes for 3.6 (fwd) Paul Walmsley
2012-06-28 12:12 ` Tony Lindgren [this message]
2012-06-28 15:54   ` 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=20120628121238.GF19842@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    /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.