Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934472AbcKQLWD (ORCPT ); Thu, 17 Nov 2016 06:22:03 -0500 Received: from mail-yb0-f174.google.com ([209.85.213.174]:33762 "EHLO mail-yb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751609AbcKQLWC (ORCPT ); Thu, 17 Nov 2016 06:22:02 -0500 MIME-Version: 1.0 In-Reply-To: <20161117104941.GA6266@mwanda> References: <1479361348-7348-1-git-send-email-sergio.paracuellos@gmail.com> <1479361348-7348-2-git-send-email-sergio.paracuellos@gmail.com> <20161117104941.GA6266@mwanda> From: Sergio Paracuellos Date: Thu, 17 Nov 2016 12:22:00 +0100 Message-ID: Subject: Re: [PATCH v3 1/2] staging: slicoss: fix different address space warnings: 32 bits To: Dan Carpenter Cc: Greg KH , devel@driverdev.osuosl.org, linux-kernel , Lior Dotan Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 602 Lines: 18 On Thu, Nov 17, 2016 at 11:51 AM, Dan Carpenter wrote: > Hm... I seem to duplicate the Sparse warnings at all. That's weird. > With this patch applied, sparse warnings dissapear for me... That's weird. > Anyway as far as I can tell the warnings are false positives... Can't > you just remove the __iomem tag? Have you tested this change? > I haven' t tested this change because I can't test it :(. Do you think that just removing __iomem tag is enough? Maybe we can get feedback from Lior or someone. Thanks for your review time, Dan. Cheers, Sergio Paracuellos