From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] OpenRISC fixes for 5.9
Date: Sat, 5 Sep 2020 22:24:05 +0900 [thread overview]
Message-ID: <20200905132405.GG3562056@lianli.shorne-pla.net> (raw)
In-Reply-To: <20200905131935.972386-1-shorne@gmail.com>
On Sat, Sep 05, 2020 at 10:19:32PM +0900, Stafford Horne wrote:
> Changes since v1:
>
> - Now a series, v1 was only the "Reserve memblock for initrd" patch
> - Added fixes for compiler issues pointed out by the kbuild robot
Forgot to mention:
- Updated "Reserve memblock for initrd", as per Mike's comments
> This is a few fixes found during testing 5.9.
>
> Stafford Horne (3):
> openrisc: Reserve memblock for initrd
> openrisc: Fix cache API compile issue when not inlining
> openrisc: Fix issue with get_user for 64-bit values
>
> arch/openrisc/include/asm/uaccess.h | 16 ++++++++--------
> arch/openrisc/kernel/setup.c | 10 ++++++++++
> arch/openrisc/mm/cache.c | 2 +-
> 3 files changed, 19 insertions(+), 9 deletions(-)
>
> --
> 2.26.2
>
prev parent reply other threads:[~2020-09-05 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 13:19 [PATCH v2 0/3] OpenRISC fixes for 5.9 Stafford Horne
2020-09-05 13:19 ` [PATCH v2 1/3] openrisc: Reserve memblock for initrd Stafford Horne
2020-09-05 13:25 ` Stafford Horne
2020-09-06 6:15 ` Mike Rapoport
2020-09-05 13:19 ` [PATCH v2 2/3] openrisc: Fix cache API compile issue when not inlining Stafford Horne
2020-09-05 13:19 ` [PATCH v2 3/3] openrisc: Fix issue with get_user for 64-bit values Stafford Horne
2020-09-05 13:57 ` Luc Van Oostenryck
2020-09-05 21:34 ` Stafford Horne
2020-09-06 0:22 ` [OpenRISC] " Luc Van Oostenryck
2020-09-06 21:00 ` Stafford Horne
2020-09-05 13:24 ` Stafford Horne [this message]
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=20200905132405.GG3562056@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=linux-kernel@vger.kernel.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).