Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S941455AbcKQLqS (ORCPT <rfc822;w@1wt.eu>);
        Thu, 17 Nov 2016 06:46:18 -0500
Received: from mail-yb0-f196.google.com ([209.85.213.196]:35903 "EHLO
        mail-yb0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932271AbcKQLqN (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 17 Nov 2016 06:46:13 -0500
MIME-Version: 1.0
In-Reply-To: <20161117113302.GU28558@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> <CAMhs-H_Q=n=x7BhesTa=mpY+k3E8KyNw-mCVfEhaoSERv-e3Gw@mail.gmail.com>
 <20161117113302.GU28558@mwanda>
From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Date: Thu, 17 Nov 2016 12:46:12 +0100
Message-ID: <CAMhs-H9jqA2k19ZAPQJTuAC77bdOXFs6gindFFJOBAtELARoFw@mail.gmail.com>
Subject: Re: [PATCH v3 1/2] staging: slicoss: fix different address space
 warnings: 32 bits
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, devel@driverdev.osuosl.org,
        linux-kernel <linux-kernel@vger.kernel.org>,
        Lior Dotan <liodot@gmail.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 360
Lines: 12

On Thu, Nov 17, 2016 at 12:33 PM, Dan Carpenter
<dan.carpenter@oracle.com> wrote:
> Give it a shot and see if the warnings go away.  I don't think the tag
> is correct.

Just removing __iomem tag in shmem_data field of slic_shmemory struct
makes sparse happy. No warnings around.

Should I send a v4 patch with the tag removed?

Cheers,
    Sergio Paracuellos