From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: hwmod fixes for v3.19-rc
Date: Tue, 20 Jan 2015 08:00:20 -0800 [thread overview]
Message-ID: <20150120160020.GB7718@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1501200647540.5450@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [150119 22:51]:
> Hi Tony
>
> On Mon, 19 Jan 2015, Tony Lindgren wrote:
>
> > * Paul Walmsley <paul@pwsan.com> [150104 15:38]:
> > > The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
> > >
> > > Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
> > >
> > > are available in the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v3.19-rc/omap-fixes-a
> > >
> > > for you to fetch changes up to 99d076b747455449b2eec9e37f3fb0bfdf51af32:
> > >
> > > MAINTAINERS: add maintainer for OMAP hwmod data (2015-01-02 16:24:27 -0700)
> > >
> > > ----------------------------------------------------------------
> > > For v3.19-rc, fix some hwmod structure details for the OMAP DSS modules
> > > for DRA7xx and AM43xx. Also update the MAINTAINERS file to encourage
> > > folks to cc me on hwmod data patches.
> > >
> > > Basic build, boot, and PM testlogs are available here:
> > >
> > > http://www.pwsan.com/omap/testlogs/omap-fixes-a-for-v3.19-rc/20150103144242/
> >
> > Paul, got any updates on this? Anyways, I'll just untag this email as
> > you asked me to wait on pulling this.
>
> At this point I think I will just requeue the remaining two valid patches
> for v3.20. Thanks for the ping
OK makes sense for me if they are not critical fixes.
Regards,
Tony
prev parent reply other threads:[~2015-01-20 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 23:35 [GIT PULL] ARM: OMAP: hwmod fixes for v3.19-rc Paul Walmsley
2015-01-19 19:43 ` Tony Lindgren
2015-01-20 6:48 ` Paul Walmsley
2015-01-20 16:00 ` 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=20150120160020.GB7718@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).