From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753633AbcLMMcQ (ORCPT ); Tue, 13 Dec 2016 07:32:16 -0500 Received: from foss.arm.com ([217.140.101.70]:50086 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753382AbcLMMcP (ORCPT ); Tue, 13 Dec 2016 07:32:15 -0500 Date: Tue, 13 Dec 2016 12:31:22 +0000 From: Mark Rutland To: Laura Abbott Cc: Ard Biesheuvel , Will Deacon , Catalin Marinas , Christoffer Dall , Marc Zyngier , Lorenzo Pieralisi , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Marek Szyprowski , Joonsoo Kim , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCHv5 06/11] arm64: Use __pa_symbol for kernel symbols Message-ID: <20161213123122.GA24607@leverpostej> References: <1481068257-6367-1-git-send-email-labbott@redhat.com> <1481068257-6367-7-git-send-email-labbott@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1481068257-6367-7-git-send-email-labbott@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 06, 2016 at 03:50:52PM -0800, Laura Abbott wrote: > > __pa_symbol is technically the marcro that should be used for kernel > symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which > will do bounds checking. > > Tested-by: James Morse > Signed-off-by: Laura Abbott This looks good to me; I have a (very minor) nit below, but either way: Reviewed-by: Mark Rutland Tested-by: Mark Rutland > diff --git a/arch/arm64/kernel/acpi_parking_protocol.c b/arch/arm64/kernel/acpi_parking_protocol.c > index a32b401..ca880ce 100644 > --- a/arch/arm64/kernel/acpi_parking_protocol.c > +++ b/arch/arm64/kernel/acpi_parking_protocol.c > @@ -18,6 +18,7 @@ > */ > #include > #include > +#include Nit: please keep includes alphabetically ordered, at least where they're ordered today. Some files are already a mess, but it would be nice to keep the well-ordered ones ordered. Thanks, Mark.