mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-xtensa@linux-xtensa.org,
	Chris Zankel <chris@zankel.net>, Marc Gauthier <marc@cadence.com>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: [PULL 0/2] Xtensa fixes for v4.9-rc6
Date: Wed, 16 Nov 2016 15:50:03 -0800	[thread overview]
Message-ID: <1479340203-23949-1-git-send-email-jcmvbkbc@gmail.com> (raw)

Hi Linus,

please pull the following two fixes for the Xtensa architecture.

The following changes since commit 712cba5d87a6c0e980ee5fad45734e189c4d7151:

  Merge tag 'v4.9-rc3' into xtensa-for-next (2016-11-06 23:31:10 -0800)

are available in the git repository at:

  git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20161116

for you to fetch changes up to 709fb1f961ea5c287107c3f903e81c9529224c8b:

  xtensa: wire up new pkey_{mprotect,alloc,free} syscalls (2016-11-14 12:31:49 -0800)

----------------------------------------------------------------
Xtensa fixes for v4.9-rc6:

- fix register dumps, stack dumps and stack traces that got torn due to
  recent printk changes;
- wire up pkey_{mprotect,alloc,free} syscalls.

----------------------------------------------------------------
Max Filippov (2):
      xtensa: clean up printk usage for boot/crash logging
      xtensa: wire up new pkey_{mprotect,alloc,free} syscalls

 arch/xtensa/include/uapi/asm/unistd.h |  9 ++++-
 arch/xtensa/kernel/time.c             | 14 +++----
 arch/xtensa/kernel/traps.c            | 74 +++++++++++------------------------
 3 files changed, 37 insertions(+), 60 deletions(-)

-- 
Thanks.
-- Max

                 reply	other threads:[~2016-11-16 23:51 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=1479340203-23949-1-git-send-email-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=chris@zankel.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=marc@cadence.com \
    --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

Powered by JetHome