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,
guoren@kernel.org
Subject: [GIT PULL] csky fixes for v5.15-rc6
Date: Sat, 16 Oct 2021 09:21:01 +0800 [thread overview]
Message-ID: <20211016012101.2862669-1-guoren@kernel.org> (raw)
Hi Linus:
The following changes since commit 64570fbc14f8d7cb3fe3995f20e26bc25ce4b2cc:
Linux 5.15-rc5 (2021-10-10 17:01:59 -0700)
are available in the Git repository at:
https://github.com/c-sky/csky-linux.git tags/csky-for-linus-5.15-rc6
for you to fetch changes up to e21e52ad1e0126e2a5e2013084ac3f47cf1e887a:
csky: Make HAVE_TCM depend on !COMPILE_TEST (2021-10-16 07:20:12 +0800)
----------------------------------------------------------------
csky updates for 5.15-rc6
Only 5 fixups:
- Make HAVE_TCM depend on !COMPILE_TEST
- bitops: Remove duplicate __clear_bit define
- Select ARCH_WANT_FRAME_POINTERS only if compiler supports it
- Fixup regs.sr broken in ptrace
- don't let sigreturn play with priveleged bits of status register
----------------------------------------------------------------
Al Viro (1):
csky: don't let sigreturn play with priveleged bits of status register
Guenter Roeck (3):
csky: Select ARCH_WANT_FRAME_POINTERS only if compiler supports it
csky: bitops: Remove duplicate __clear_bit define
csky: Make HAVE_TCM depend on !COMPILE_TEST
Guo Ren (1):
csky: Fixup regs.sr broken in ptrace
arch/csky/Kconfig | 3 ++-
arch/csky/include/asm/bitops.h | 1 -
arch/csky/kernel/ptrace.c | 3 ++-
arch/csky/kernel/signal.c | 4 ++++
4 files changed, 8 insertions(+), 3 deletions(-)
next reply other threads:[~2021-10-16 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 1:21 guoren [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-16 1:06 [GIT PULL] csky fixes for v5.15-rc6 guoren
2021-10-16 16:23 ` 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=20211016012101.2862669-1-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).