linux-csky.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: guoren@kernel.org
To: torvalds@linux-foundation.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-csky@vger.kernel.org
Subject: [GIT PULL] csky updates for v5.7-rc8
Date: Thu, 28 May 2020 08:59:32 +0800	[thread overview]
Message-ID: <1590627572-10100-1-git-send-email-guoren@kernel.org> (raw)

Hi Linus,

Please pull the 4 fixups for v5.7-rc8.

Best Regards
 Guo Ren

The following changes since commit 9cb1fd0efd195590b828b9b865421ad345a4a145:

  Linux 5.7-rc7 (2020-05-24 15:32:54 -0700)

are available in the git repository at:

  https://github.com/c-sky/csky-linux.git tags/csky-for-linus-5.7-rc8

for you to fetch changes up to f36e0aab6f1f78d770ce859df3f07a9c5763ce5f:

  csky: Fixup CONFIG_DEBUG_RSEQ (2020-05-28 00:18:36 +0000)

----------------------------------------------------------------
csky updates for 5.7-rc8

Another 4 fixups for csky:
 - fixup req_syscall debug
 - fixup abiv2 syscall_trace
 - fixup preempt enable
 - Cleanup regs usage in entry.S

----------------------------------------------------------------
Guo Ren (4):
      csky: Fixup CONFIG_PREEMPT panic
      csky: Fixup abiv2 syscall_trace break a4 & a5
      csky: Coding convention in entry.S
      csky: Fixup CONFIG_DEBUG_RSEQ

 arch/csky/abiv1/inc/abi/entry.h     |   6 --
 arch/csky/abiv2/inc/abi/entry.h     |   8 +--
 arch/csky/include/asm/thread_info.h |   6 ++
 arch/csky/kernel/entry.S            | 117 ++++++++++++++++++------------------
 4 files changed, 66 insertions(+), 71 deletions(-)

             reply	other threads:[~2020-05-28  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28  0:59 guoren [this message]
2020-05-28 21:10 ` [GIT PULL] csky updates for v5.7-rc8 pr-tracker-bot

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=1590627572-10100-1-git-send-email-guoren@kernel.org \
    --to=guoren@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-csky@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).