From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752113AbbD3OvQ (ORCPT <rfc822;w@1wt.eu>);
	Thu, 30 Apr 2015 10:51:16 -0400
Received: from mail.linuxfoundation.org ([140.211.169.12]:43299 "EHLO
	mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751251AbbD3OvJ (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 30 Apr 2015 10:51:09 -0400
Date: Thu, 30 Apr 2015 16:51:03 +0200
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Garret Kelly <gdk@google.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
        Noralf =?iso-8859-1?Q?Tr=F8nnes?= <noralf@tronnes.org>,
        "open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
        open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: fbtft: force cast to non-__iomem pointer
Message-ID: <20150430145103.GA18896@kroah.com>
References: <1429205359-12929-1-git-send-email-gdk@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1429205359-12929-1-git-send-email-gdk@google.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Apr 16, 2015 at 01:29:19PM -0400, Garret Kelly wrote:
> fbtft uses fb_info's screen_base field to store a non-__iomem
> allocation.  Cast away the __iomem qualifier when freeing the pointer to
> suppress the sparse warning.

Can't we fix this properly, to use the correct type of pointer instead
for non-__iomem allocations?

thanks,

greg k-h