From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753083AbbCWNz1 (ORCPT ); Mon, 23 Mar 2015 09:55:27 -0400 Received: from mail-pa0-f44.google.com ([209.85.220.44]:34554 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752028AbbCWNzX (ORCPT ); Mon, 23 Mar 2015 09:55:23 -0400 Date: Mon, 23 Mar 2015 19:25:16 +0530 From: Sudip Mukherjee To: Lorenzo Stoakes Cc: teddy.wang@siliconmotion.com, gregkh@linuxfoundation.org, linux-fbdev@vger.kernel.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RESEND 2 1/5] staging: sm750fb: Use memset_io instead of memset Message-ID: <20150323135516.GB27897@sudip-PC> References: <1426864935-29350-1-git-send-email-lstoakes@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1426864935-29350-1-git-send-email-lstoakes@gmail.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 Fri, Mar 20, 2015 at 03:22:11PM +0000, Lorenzo Stoakes wrote: > This patch takes into account that cursor->vstart, crtc->vScreen and > share->pvMem are pointers to memory-mapped I/O and thus we should use memset_io > to make this explicit. In addition, some architectures require special treatment > of memory-mapped I/O so the previous code could actually break without this > change. sorry for the confusion. tested the whole series on hardware. Tested-by: Sudip Mukherjee sudip