From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: more fixes intended for 3.5-rc
Date: Thu, 5 Jul 2012 02:27:21 -0700 [thread overview]
Message-ID: <20120705092721.GX1122@atomide.com> (raw)
In-Reply-To: <20120705085229.GV1122@atomide.com>
* Tony Lindgren <tony@atomide.com> [120705 01:57]:
> * Arnd Bergmann <arnd@arndb.de> [120705 01:41]:
> > On Thursday 05 July 2012, Tony Lindgren wrote:
> > > * Paul Walmsley <paul@pwsan.com> [120704 07:13]:
> > > > Hi Tony
> > > >
> > > > The following changes since commit 6887a4131da3adaab011613776d865f4bcfb5678:
> > > >
> > > > Linux 3.5-rc5 (2012-06-30 16:08:57 -0700)
> > > >
> > > > are available in the git repository at:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-fixes-b-for-3.5rc
> > > >
> > > > for you to fetch changes up to d7a0b5133f6b1d53d693b9b9873e64e3c8f0db0e:
> > > >
> > > > ARM: OMAP2+: hwmod data: Fix wrong McBSP clock alias on OMAP4 (2012-07-04 06:55:29 -0600)
> > > >
> > > Thanks pulling into fixes.
> >
> > I'm planning to send a set of fixes upstream to Linus today. Should I
> > pull your fixes branch before that?
>
> It seems it should be safe to do, I'll take one more look and send
> a separate pull request shortly.
OK, sent a pull request with Subject: [GIT PULL] omap fixes for v3.5-rc5
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-07-05 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 14:08 [GIT PULL] ARM: OMAP2+: more fixes intended for 3.5-rc Paul Walmsley
2012-07-05 8:15 ` Tony Lindgren
2012-07-05 8:36 ` Arnd Bergmann
2012-07-05 8:52 ` Tony Lindgren
2012-07-05 9:27 ` Tony Lindgren [this message]
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=20120705092721.GX1122@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).