linux-kernel.vger.kernel.org archive mirror
 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.11
Date: Fri, 22 Jan 2021 09:29:02 +0900	[thread overview]
Message-ID: <20210122002902.GP2002709@lianli.shorne-pla.net> (raw)

Hi Linus,

Please consider for pull:

The following changes since commit 7c53f6b671f4aba70ff15e1b05148b10d58c2837:

  Linux 5.11-rc3 (2021-01-10 14:34:50 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 031c7a8cd6fc565e90320bf08f22ee6e70f9d969:

  openrisc: io: Add missing __iomem annotation to iounmap() (2021-01-20 06:14:26 +0900)

----------------------------------------------------------------
OpenRISC fixes for 5.11

Fixes include:
 * Compiler warning fixup for new Litex SoC driver
 * Sparse warning fixup for iounmap

----------------------------------------------------------------
Geert Uytterhoeven (1):
      openrisc: io: Add missing __iomem annotation to iounmap()

Stafford Horne (1):
      soc: litex: Fix compile warning when device tree is not configured

 arch/openrisc/include/asm/io.h     | 2 +-
 arch/openrisc/mm/ioremap.c         | 2 +-
 drivers/soc/litex/litex_soc_ctrl.c | 3 ++-
 3 files changed, 4 insertions(+), 3 deletions(-)

-Stafford

             reply	other threads:[~2021-01-22  0:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  0:29 Stafford Horne [this message]
2021-01-22  2:41 ` [GIT PULL] OpenRISC fixes for 5.11 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=20210122002902.GP2002709@lianli.shorne-pla.net \
    --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 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).