From: Tony Lindgren <tony@atomide.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 6/6] am33xx changes for v3.6 merge window
Date: Tue, 3 Jul 2012 23:41:53 -0700 [thread overview]
Message-ID: <20120704064152.GN1122@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA6237A@DBDE01.ent.ti.com>
* Hiremath, Vaibhav <hvaibhav@ti.com> [120703 05:00]:
> On Tue, Jul 03, 2012 at 17:18:56, Tony Lindgren wrote:
> > * Vaibhav Hiremath <hvaibhav@ti.com> [120703 04:37]:
> > >
> > > Few patches got missed in this pull request,
> > >
> > > ARM: OMAP2+: am33xx: Make am33xx as a separate class
> > > ARM: OMAP2+: am33xx: Change cpu_is_am33xx to soc_is_am33xx
> >
> > OK, at least the first needs to be rebased to apply.
> >
> > Can you please refresh those against current devel-am33xx
> > branch at commit 6fd8246b1c1167c983b089f9eaafa13ef9ca7adf and
> > repost?
> >
> > I'll do a separate pull request for those once they are
> > ready.
> >
>
> Thanks Tony, I will resubmit them again today.
> Also, request you to review and merge Cleanup patch-series I had posted
> few days back.
Yes thanks will look.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 6/6] am33xx changes for v3.6 merge window
Date: Tue, 3 Jul 2012 23:41:53 -0700 [thread overview]
Message-ID: <20120704064152.GN1122@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA6237A@DBDE01.ent.ti.com>
* Hiremath, Vaibhav <hvaibhav@ti.com> [120703 05:00]:
> On Tue, Jul 03, 2012 at 17:18:56, Tony Lindgren wrote:
> > * Vaibhav Hiremath <hvaibhav@ti.com> [120703 04:37]:
> > >
> > > Few patches got missed in this pull request,
> > >
> > > ARM: OMAP2+: am33xx: Make am33xx as a separate class
> > > ARM: OMAP2+: am33xx: Change cpu_is_am33xx to soc_is_am33xx
> >
> > OK, at least the first needs to be rebased to apply.
> >
> > Can you please refresh those against current devel-am33xx
> > branch at commit 6fd8246b1c1167c983b089f9eaafa13ef9ca7adf and
> > repost?
> >
> > I'll do a separate pull request for those once they are
> > ready.
> >
>
> Thanks Tony, I will resubmit them again today.
> Also, request you to review and merge Cleanup patch-series I had posted
> few days back.
Yes thanks will look.
Regards,
Tony
next prev parent reply other threads:[~2012-07-04 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1SlGLI-0004Vt-0L@merlin.infradead.org>
2012-07-03 11:32 ` [GIT PULL 6/6] am33xx changes for v3.6 merge window Vaibhav Hiremath
2012-07-03 11:32 ` Vaibhav Hiremath
2012-07-03 11:48 ` Tony Lindgren
2012-07-03 11:48 ` Tony Lindgren
2012-07-03 11:55 ` Hiremath, Vaibhav
2012-07-03 11:55 ` Hiremath, Vaibhav
2012-07-04 6:41 ` Tony Lindgren [this message]
2012-07-04 6:41 ` Tony Lindgren
2012-07-01 9:01 [GIT PULL 1/6] omap non-critical fixes " Tony Lindgren
2012-07-01 9:01 ` [GIT PULL 6/6] am33xx changes " Tony Lindgren
2012-07-01 9:01 ` 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=20120704064152.GN1122@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
/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.