linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: torvalds@linux-foundation.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] MIPS fixes for v5.13
Date: Fri, 28 May 2021 13:54:09 +0200	[thread overview]
Message-ID: <20210528115409.GA8447@alpha.franken.de> (raw)

The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:

  Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_5.13_1

for you to fetch changes up to 78cf0eb926cb1abeff2106bae67752e032fe5f3e:

  MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER (2021-05-25 15:33:17 +0200)

----------------------------------------------------------------
- fixed function/preempt traces hangs
- a few build fixes

----------------------------------------------------------------
Randy Dunlap (3):
      MIPS: alchemy: xxs1500: add gpio-au1000.h header file
      MIPS: launch.h: add include guard to prevent build errors
      MIPS: ralink: export rt_sysc_membase for rt2880_wdt.c

Tiezhu Yang (1):
      MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER

 arch/mips/alchemy/board-xxs1500.c          |  1 +
 arch/mips/include/asm/mips-boards/launch.h |  5 +++++
 arch/mips/lib/mips-atomic.c                | 12 ++++++------
 arch/mips/ralink/of.c                      |  2 ++
 4 files changed, 14 insertions(+), 6 deletions(-)
-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

             reply	other threads:[~2021-05-28 11:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 11:54 Thomas Bogendoerfer [this message]
2021-05-28 18:59 ` [GIT PULL] MIPS fixes for v5.13 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=20210528115409.GA8447@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@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).