mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ley Foon Tan <lftan@altera.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"lftan.linux@gmail.com" <lftan.linux@gmail.com>
Subject: [GIT PULL] arch/nios2 fixes for v4.0
Date: Fri, 10 Apr 2015 15:31:32 +0800	[thread overview]
Message-ID: <1428651092.2306.6.camel@leyfoon-vm> (raw)

Hi Linus

There are 3 arch/nios2 fixes for 4.0 final:

- fix cache coherency issue when debugging with gdb
- move restart_block to struct task_struct (aligned with other architectures)
- fix for missing registers defines for ptrace

Please consider pulling.


Regards
Ley Foon


The following changes since commit f22e6e847115abc3a0e2ad7bb18d243d42275af1:

  Linux 4.0-rc7 (2015-04-06 15:39:45 -0700)

are available in the git repository at:

  git://git.rocketboards.org/linux-socfpga-next.git tags/nios2-fixes-v4.0-final

for you to fetch changes up to 4a89c3088ff61aa24754e9cd6dc665cc719f7efe:

  nios2: fix cache coherency issue when debug with gdb (2015-04-10 11:10:08 +0800)

----------------------------------------------------------------
nios2 fixes for v4.0-final

----------------------------------------------------------------
Ley Foon Tan (3):
      nios2: signal: Move restart_block to struct task_struct
      nios2: add missing ptrace registers defines
      nios2: fix cache coherency issue when debug with gdb

 arch/nios2/include/asm/thread_info.h | 4 ----
 arch/nios2/include/uapi/asm/ptrace.h | 9 +++++++--
 arch/nios2/kernel/entry.S            | 2 +-
 arch/nios2/kernel/signal.c           | 2 +-
 arch/nios2/mm/cacheflush.c           | 3 ---
 5 files changed, 9 insertions(+), 11 deletions(-)

                 reply	other threads:[~2015-04-10  9:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1428651092.2306.6.camel@leyfoon-vm \
    --to=lftan@altera.com \
    --cc=lftan.linux@gmail.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

all inboxes | Powered by JetHome®