public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <Catalin.Marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] arm64 fixes for 3.8
Date: Wed, 23 Jan 2013 17:27:04 +0000	[thread overview]
Message-ID: <20130123172703.GJ27474@arm.com> (raw)

Hi Linus,

Please pull the arm64 fixes below. Thanks.

The following changes since commit 7d1f9aeff1ee4a20b1aeb377dd0f579fe9647619:

  Linux 3.8-rc4 (2013-01-17 19:25:45 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git tags/arm64-fixes

for you to fetch changes up to f1b99392caf120d7533da260318fae0eb5053737:

  arm64: makefile: fix uname munging when setting ARCH on native machine (2013-01-22 17:51:00 +0000)

----------------------------------------------------------------
- ELF coredump fix (more registers dumped than what user space expects)
- SUBARCH name generation (s/aarch64/arm64/)

----------------------------------------------------------------
Will Deacon (2):
      arm64: elf: fix core dumping to match what glibc expects
      arm64: makefile: fix uname munging when setting ARCH on native machine

 Makefile                     | 2 +-
 arch/arm64/include/asm/elf.h | 5 ++++-
 tools/perf/Makefile          | 2 +-
 3 files changed, 6 insertions(+), 3 deletions(-)

             reply	other threads:[~2013-01-23 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 17:27 Catalin Marinas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-15 18:20 [GIT PULL] arm64 fixes for 3.8 Catalin Marinas
2013-01-04 15:45 Catalin Marinas

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=20130123172703.GJ27474@arm.com \
    --to=catalin.marinas@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox