Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 27 Nov 2020 10:32:24 +0100
From:   Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To:     Jinyang He <hejinyang@loongson.cn>
Cc:     linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
        Sergei Shtylyov <sergei.shtylyov@gmail.com>
Subject: Re: [PATCH v2 0/2] IPS: Fix up apply_r_mips_26_rel and add KASLR
 support for Loongson64
Message-ID: <20201127093223.GA4859@alpha.franken.de>
References: <1606298812-6928-1-git-send-email-hejinyang@loongson.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1606298812-6928-1-git-send-email-hejinyang@loongson.cn>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Wed, Nov 25, 2020 at 06:06:52PM +0800, Jinyang He wrote:
> Abandon the third patch in v1. There are many other factors that should
> be considered. If possible, I'll fix it later.
> 
> Jinyang He (2):
>   MIPS: KASLR: Correcte valid bits in apply_r_mips_26_rel()
>   MIPS: Loongson64: Add KASLR support
> 
>  arch/mips/Kconfig           |  5 ++++-
>  arch/mips/kernel/relocate.c | 11 +++++++++--
>  2 files changed, 13 insertions(+), 3 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]