mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	devel@driverdev.osuosl.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Lior Dotan <liodot@gmail.com>
Subject: Re: [PATCH v3 1/2] staging: slicoss: fix different address space warnings: 32 bits
Date: Fri, 18 Nov 2016 08:45:04 +0100	[thread overview]
Message-ID: <20161118074504.GA15290@kroah.com> (raw)
In-Reply-To: <CAMhs-H9jqA2k19ZAPQJTuAC77bdOXFs6gindFFJOBAtELARoFw@mail.gmail.com>

On Thu, Nov 17, 2016 at 12:46:12PM +0100, Sergio Paracuellos wrote:
> 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?

Yes, please fix up this series and resend.

thanks,

greg k-h

  reply	other threads:[~2016-11-18  7:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17  5:42 [PATCH v3 0/2] staging: slicoss: fix different address space warnings Sergio Paracuellos
2016-11-17  5:42 ` [PATCH v3 1/2] staging: slicoss: fix different address space warnings: 32 bits Sergio Paracuellos
2016-11-17 10:51   ` Dan Carpenter
2016-11-17 11:22     ` Sergio Paracuellos
2016-11-17 11:33       ` Dan Carpenter
2016-11-17 11:46         ` Sergio Paracuellos
2016-11-18  7:45           ` Greg KH [this message]
2016-11-17  5:42 ` [PATCH v3 2/2] staging: slicoss: fix different address space warnings: 64 bits Sergio Paracuellos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161118074504.GA15290@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liodot@gmail.com \
    --cc=sergio.paracuellos@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome