From: Chris Metcalf <cmetcalf@tilera.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: [GIT PULL] arch/tile fixes for 2.6.36
Date: Fri, 24 Sep 2010 18:34:02 -0400 [thread overview]
Message-ID: <4C9D275A.5030405@tilera.com> (raw)
Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git stable
to get one toolchain-related bug fix for arch/tile/ for 2.6.36. The commit
describes the problem, but basically a good fix in our compiler causes a
mysterious failure in our assembler, and conveniently, removing some dead
code in an assembly file avoids having to back out the good fix, as well as
allowing the existing toolchain to compile 2.6.36.
Thanks!
Chris Metcalf (1):
arch/tile: remove dead code from intvec_32.S
arch/tile/kernel/intvec_32.S | 7 -------
1 files changed, 0 insertions(+), 7 deletions(-)
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next reply other threads:[~2010-09-24 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 22:34 Chris Metcalf [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-15 15:34 [GIT PULL] arch/tile fixes for 2.6.36 Chris Metcalf
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=4C9D275A.5030405@tilera.com \
--to=cmetcalf@tilera.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.