From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Garret Kelly <gdk@google.com>
Cc: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Noralf Trønnes" <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
Date: Thu, 30 Apr 2015 16:51:03 +0200 [thread overview]
Message-ID: <20150430145103.GA18896@kroah.com> (raw)
In-Reply-To: <1429205359-12929-1-git-send-email-gdk@google.com>
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
next prev parent reply other threads:[~2015-04-30 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 17:29 [PATCH] staging: fbtft: force cast to non-__iomem pointer Garret Kelly
2015-04-30 14:51 ` Greg Kroah-Hartman [this message]
2015-05-06 21:34 ` Garret Kelly
2015-05-07 8:39 ` Dan Carpenter
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=20150430145103.GA18896@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gdk@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=thomas.petazzoni@free-electrons.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