All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Openrisc <openrisc@lists.librecores.org>
Subject: [GIT PULL] OpenRISC fixes for 5.13
Date: Fri, 21 May 2021 16:16:52 +0900	[thread overview]
Message-ID: <YKdeZFKthTY31705@antec> (raw)

Hi Linus,

Please consider for pull

The following changes since commit 9f4ad9e425a1d3b6a34617b8ea226d56a119a717:

  Linux 5.12 (2021-04-25 13:49:08 -0700)

are available in the Git repository at:

  git://github.com/openrisc/linux.git tags/for-linus

for you to fetch changes up to 8b549c18ae81dbc36fb11e4aa08b8378c599ca95:

  openrisc: Define memory barrier mb (2021-05-15 16:00:10 +0900)

----------------------------------------------------------------
OpenRISC fixes for 5.13

A few fixes that came in around the time of the merge
window.

----------------------------------------------------------------
Christophe JAILLET (1):
      openrisc: Fix a memory leak

Mike Rapoport (2):
      openrisc: mm/init.c: remove unused memblock_region variable in map_ram()
      openrisc: mm/init.c: remove unused variable 'end' in paging_init()

Peter Zijlstra (1):
      openrisc: Define memory barrier mb

 arch/openrisc/include/asm/barrier.h | 9 +++++++++
 arch/openrisc/kernel/setup.c        | 2 ++
 arch/openrisc/mm/init.c             | 6 +-----
 3 files changed, 12 insertions(+), 5 deletions(-)
 create mode 100644 arch/openrisc/include/asm/barrier.h

WARNING: multiple messages have this Message-ID (diff)
From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [GIT PULL] OpenRISC fixes for 5.13
Date: Fri, 21 May 2021 16:16:52 +0900	[thread overview]
Message-ID: <YKdeZFKthTY31705@antec> (raw)

Hi Linus,

Please consider for pull

The following changes since commit 9f4ad9e425a1d3b6a34617b8ea226d56a119a717:

  Linux 5.12 (2021-04-25 13:49:08 -0700)

are available in the Git repository at:

  git://github.com/openrisc/linux.git tags/for-linus

for you to fetch changes up to 8b549c18ae81dbc36fb11e4aa08b8378c599ca95:

  openrisc: Define memory barrier mb (2021-05-15 16:00:10 +0900)

----------------------------------------------------------------
OpenRISC fixes for 5.13

A few fixes that came in around the time of the merge
window.

----------------------------------------------------------------
Christophe JAILLET (1):
      openrisc: Fix a memory leak

Mike Rapoport (2):
      openrisc: mm/init.c: remove unused memblock_region variable in map_ram()
      openrisc: mm/init.c: remove unused variable 'end' in paging_init()

Peter Zijlstra (1):
      openrisc: Define memory barrier mb

 arch/openrisc/include/asm/barrier.h | 9 +++++++++
 arch/openrisc/kernel/setup.c        | 2 ++
 arch/openrisc/mm/init.c             | 6 +-----
 3 files changed, 12 insertions(+), 5 deletions(-)
 create mode 100644 arch/openrisc/include/asm/barrier.h

             reply	other threads:[~2021-05-21  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  7:16 Stafford Horne [this message]
2021-05-21  7:16 ` [OpenRISC] [GIT PULL] OpenRISC fixes for 5.13 Stafford Horne
2021-05-21 16:34 ` pr-tracker-bot
2021-05-21 16:34   ` [OpenRISC] " 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=YKdeZFKthTY31705@antec \
    --to=shorne@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.