From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Tony Lindgren <tony@atomide.com>,
arm@kernel.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] Few regression fixes for omaps for v3.16-rc series
Date: Thu, 24 Jul 2014 14:07:43 +0200 [thread overview]
Message-ID: <5087610.iA71nMtfdT@wuerfel> (raw)
In-Reply-To: <20140724114348.GA29045@atomide.com>
On Thursday 24 July 2014 04:43:49 Tony Lindgren wrote:
> Two regression fixes for omaps and one fix for device signaling:
>
> - L2 cache regression fix for a warning about trying to access
> a read-only register
>
> - GPMC ECC software fallback regression fix for omap3
>
> - Fix for dra7 pinctrl pull-up direction that causes signal issues
> for anybody trying to use the internal pull up or down
>
Merged into the fixes branch, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Few regression fixes for omaps for v3.16-rc series
Date: Thu, 24 Jul 2014 14:07:43 +0200 [thread overview]
Message-ID: <5087610.iA71nMtfdT@wuerfel> (raw)
In-Reply-To: <20140724114348.GA29045@atomide.com>
On Thursday 24 July 2014 04:43:49 Tony Lindgren wrote:
> Two regression fixes for omaps and one fix for device signaling:
>
> - L2 cache regression fix for a warning about trying to access
> a read-only register
>
> - GPMC ECC software fallback regression fix for omap3
>
> - Fix for dra7 pinctrl pull-up direction that causes signal issues
> for anybody trying to use the internal pull up or down
>
Merged into the fixes branch, thanks!
Arnd
next prev parent reply other threads:[~2014-07-24 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 11:43 [GIT PULL] Few regression fixes for omaps for v3.16-rc series Tony Lindgren
2014-07-24 11:43 ` Tony Lindgren
2014-07-24 12:07 ` Arnd Bergmann [this message]
2014-07-24 12:07 ` Arnd Bergmann
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=5087610.iA71nMtfdT@wuerfel \
--to=arnd@arndb.de \
--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.