From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] omap wake-up regression fix for v3.17
Date: Mon, 22 Sep 2014 21:58:56 -0700 [thread overview]
Message-ID: <20140923045856.GE7487@localhost> (raw)
In-Reply-To: <20140918201708.GP14505@atomide.com>
On Thu, Sep 18, 2014 at 01:17:08PM -0700, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [140917 08:00]:
> > The following changes since commit 69e273c0b0a3c337a521d083374c918dc52c666f:
> >
> > Linux 3.17-rc3 (2014-08-31 18:23:04 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/fix-v3.17-io-chain-v3
> >
> > for you to fetch changes up to 7db143b89137de06ed289cf8b302f3bbbc5baa1f:
> >
> > ARM: OMAP3: Fix I/O chain clock line assertion timed out error (2014-09-16 15:09:44 -0700)
> >
> > ----------------------------------------------------------------
> > Regression fix for early omap3 revisions for wake-up events that
> > too some time to narrow down. Although a bit intrusive, this would
> > be good to get into the -rc cycle as there are quite a few boards
> > out there with omap3 es2.1 and es3.0, and we have those in at least
> > three boot test systems too that show errors without this patch.
>
> This can also cause a merge conflict for linux next,
> here's the merge resolution for reference.
Merged, thanks.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap wake-up regression fix for v3.17
Date: Mon, 22 Sep 2014 21:58:56 -0700 [thread overview]
Message-ID: <20140923045856.GE7487@localhost> (raw)
In-Reply-To: <20140918201708.GP14505@atomide.com>
On Thu, Sep 18, 2014 at 01:17:08PM -0700, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [140917 08:00]:
> > The following changes since commit 69e273c0b0a3c337a521d083374c918dc52c666f:
> >
> > Linux 3.17-rc3 (2014-08-31 18:23:04 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/fix-v3.17-io-chain-v3
> >
> > for you to fetch changes up to 7db143b89137de06ed289cf8b302f3bbbc5baa1f:
> >
> > ARM: OMAP3: Fix I/O chain clock line assertion timed out error (2014-09-16 15:09:44 -0700)
> >
> > ----------------------------------------------------------------
> > Regression fix for early omap3 revisions for wake-up events that
> > too some time to narrow down. Although a bit intrusive, this would
> > be good to get into the -rc cycle as there are quite a few boards
> > out there with omap3 es2.1 and es3.0, and we have those in at least
> > three boot test systems too that show errors without this patch.
>
> This can also cause a merge conflict for linux next,
> here's the merge resolution for reference.
Merged, thanks.
-Olof
next prev parent reply other threads:[~2014-09-23 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 14:59 [GIT PULL] omap wake-up regression fix for v3.17 Tony Lindgren
2014-09-17 14:59 ` Tony Lindgren
2014-09-18 20:17 ` Tony Lindgren
2014-09-18 20:17 ` Tony Lindgren
2014-09-23 4:58 ` Olof Johansson [this message]
2014-09-23 4:58 ` Olof Johansson
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=20140923045856.GE7487@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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.