From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753118AbcBPLOj (ORCPT ); Tue, 16 Feb 2016 06:14:39 -0500 Received: from foss.arm.com ([217.140.101.70]:52199 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751587AbcBPLOi (ORCPT ); Tue, 16 Feb 2016 06:14:38 -0500 Date: Tue, 16 Feb 2016 11:14:26 +0000 From: Brian Starkey To: Greg Kroah-Hartman Cc: Catalin Marinas , Dan Williams , Andrew Morton , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [RESEND2 PATCH 1/3] memremap: add MEMREMAP_WC flag Message-ID: <20160216111426.GA22133@e106950-lin.cambridge.arm.com> References: <9085d37fa97a762a46b9d58719c085368682c64f.1454950917.git.brian.starkey@arm.com> <20160208183006.GA8429@kroah.com> <20160209091501.GA23507@e106950-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20160209091501.GA23507@e106950-lin.cambridge.arm.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 Hi Greg, Is the documentation OK? Is there any chance of you picking up this series? I can rebase onto -next if that's the right place, but they still apply on 4.5-rc4 and fix a panic, so I thought perhaps they could make 4.5. Thanks, Brian On Tue, Feb 09, 2016 at 09:15:02AM +0000, Brian Starkey wrote: >Hi Greg, > >On Mon, Feb 08, 2016 at 10:30:06AM -0800, Greg KH wrote: >>On Mon, Feb 08, 2016 at 05:30:50PM +0000, Brian Starkey wrote: >>>diff --git a/include/linux/io.h b/include/linux/io.h >>>index 32403b5..e2c8419 100644 >>>--- a/include/linux/io.h >>>+++ b/include/linux/io.h >>>@@ -135,6 +135,7 @@ enum { >>> /* See memremap() kernel-doc for usage description... */ >>> MEMREMAP_WB = 1 << 0, >>> MEMREMAP_WT = 1 << 1, >>>+ MEMREMAP_WC = 1 << 2, >> >>You didn't update the documentation :( >> > >Maybe I missed something, but I don't think there's anything to update >here? Like the comment says, the flags are documented in the memremap() >kernel-doc (which I did update - see the next two hunks of this patch). > >Thanks, > >Brian From mboxrd@z Thu Jan 1 00:00:00 1970 From: brian.starkey@arm.com (Brian Starkey) Date: Tue, 16 Feb 2016 11:14:26 +0000 Subject: [RESEND2 PATCH 1/3] memremap: add MEMREMAP_WC flag In-Reply-To: <20160209091501.GA23507@e106950-lin.cambridge.arm.com> References: <9085d37fa97a762a46b9d58719c085368682c64f.1454950917.git.brian.starkey@arm.com> <20160208183006.GA8429@kroah.com> <20160209091501.GA23507@e106950-lin.cambridge.arm.com> Message-ID: <20160216111426.GA22133@e106950-lin.cambridge.arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Greg, Is the documentation OK? Is there any chance of you picking up this series? I can rebase onto -next if that's the right place, but they still apply on 4.5-rc4 and fix a panic, so I thought perhaps they could make 4.5. Thanks, Brian On Tue, Feb 09, 2016 at 09:15:02AM +0000, Brian Starkey wrote: >Hi Greg, > >On Mon, Feb 08, 2016 at 10:30:06AM -0800, Greg KH wrote: >>On Mon, Feb 08, 2016 at 05:30:50PM +0000, Brian Starkey wrote: >>>diff --git a/include/linux/io.h b/include/linux/io.h >>>index 32403b5..e2c8419 100644 >>>--- a/include/linux/io.h >>>+++ b/include/linux/io.h >>>@@ -135,6 +135,7 @@ enum { >>> /* See memremap() kernel-doc for usage description... */ >>> MEMREMAP_WB = 1 << 0, >>> MEMREMAP_WT = 1 << 1, >>>+ MEMREMAP_WC = 1 << 2, >> >>You didn't update the documentation :( >> > >Maybe I missed something, but I don't think there's anything to update >here? Like the comment says, the flags are documented in the memremap() >kernel-doc (which I did update - see the next two hunks of this patch). > >Thanks, > >Brian