From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] ARM: OMAP5: Add minimal OMAP5 SOC support for 3.6
Date: Tue, 7 Aug 2012 00:00:57 -0700 [thread overview]
Message-ID: <20120807070056.GI11011@atomide.com> (raw)
In-Reply-To: <CAMQu2gwNeYUm7iL+30wwoHCNGZ3dXF2k+w-PE=tw-pMSO9F3NQ@mail.gmail.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [120726 00:27]:
> On Tue, Jul 10, 2012 at 10:33 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * Santosh Shilimkar <santosh.shilimkar@ti.com> [120709 08:07]:
> >> Tony,
> >>
> >> Please pull below OMAP5 SOC minimal support. It is generated against the
> >> cleanup-part2 branch of yours. As you suggested, I have dropped CK_54XX
> >> flag changes to avoid conflicts.
> >
> > OK seems to merge fine now, pulled into devel-omap5.
> >
> Now OMAP5 support appearing in mainline. In case you would like
> to boot mainline on your OMAP5 board, you need to merge a
> OMAP5 SOC hwmod/clock data which is out of tree. I have
> put that on a branch and same is available [1]. Please note
> that the only DT boot supported.
Nice to see it being a small set :) Have these changes been
posted to the mailing lists for review?
Regards,
Tony
> [1] git://github.com/SantoshShilimkar/linux.git out-of-tree/omap5-data
next prev parent reply other threads:[~2012-08-07 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 15:02 [GIT PULL] ARM: OMAP5: Add minimal OMAP5 SOC support for 3.6 Santosh Shilimkar
2012-07-09 15:02 ` Santosh Shilimkar
2012-07-10 8:33 ` Tony Lindgren
2012-07-10 8:33 ` Tony Lindgren
2012-07-10 8:43 ` Shilimkar, Santosh
2012-07-10 8:43 ` Shilimkar, Santosh
2012-07-26 7:22 ` Shilimkar, Santosh
2012-08-07 7:00 ` Tony Lindgren [this message]
2012-08-07 7:16 ` Shilimkar, Santosh
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=20120807070056.GI11011@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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.