From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-SH <linux-sh@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>
Subject: [PATCH resend 0/3] SH: compile fixup patches
Date: 20 Jan 2020 10:21:46 +0900 [thread overview]
Message-ID: <87o8uyylat.wl-kuninori.morimoto.gx@renesas.com> (raw)
Hi Andrew
Cc: Yoshinori, Rich
I'm posting these patches to SH ML from few month ago,
but SH maintainer is not working in these days...
Is it possible to consider about these ?
SH compile will be fail without these patchese.
I have +1 patch, but will has conflict to Geert's this patch,
thus, I'm skipping it now.
iomap: Constify ioreadX() iomem argument (as in generic implementation)
https://lore.kernel.org/lkml/20200108200528.4614-2-krzk@kernel.org/
Kuninori Morimoto (3):
sh: Add missing DECLARE_EXPORT() for __ashiftrt_r4_xx
sh: Convert iounmap() macros to inline functions
sh: Convert ins[bwl]/outs[bwl] macros to inline functions
arch/sh/include/asm/io.h | 2 +-
arch/sh/include/asm/io_noioport.h | 34 ++++++++++++++++++++++++++++------
arch/sh/kernel/sh_ksyms_32.c | 17 +++++++++++++++++
3 files changed, 46 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2020-01-20 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 1:21 Kuninori Morimoto [this message]
2020-01-20 1:22 ` [PATCH resend 1/3] sh: Add missing DECLARE_EXPORT() for __ashiftrt_r4_xx Kuninori Morimoto
2020-01-20 1:22 ` [PATCH resend 2/3] sh: Convert iounmap() macros to inline functions Kuninori Morimoto
2020-01-20 8:28 ` Sergei Shtylyov
2020-01-20 1:22 ` [PATCH resend 3/3] sh: Convert ins[bwl]/outs[bwl] " Kuninori Morimoto
2020-01-22 1:51 ` [PATCH resend 0/3] SH: compile fixup patches Rob Landley
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=87o8uyylat.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).