On Tue, 4 Sep 2012, Kent Yoder wrote:
> acpi_os_map_memory expects its return value to be in the __iomem address
> space. Tag the variable we're using as such and use memcpy_fromio to
> avoid further sparse warnings.
>
> Signed-off-by: Kent Yoder
Applied to
On Tue, 4 Sep 2012, Kent Yoder wrote:
acpi_os_map_memory expects its return value to be in the __iomem address
space. Tag the variable we're using as such and use memcpy_fromio to
avoid further sparse warnings.
Signed-off-by: Kent Yoder k...@linux.vnet.ibm.com
Applied to
acpi_os_map_memory expects its return value to be in the __iomem address
space. Tag the variable we're using as such and use memcpy_fromio to
avoid further sparse warnings.
Signed-off-by: Kent Yoder
---
drivers/char/tpm/tpm_acpi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
On Sun, Sep 02, 2012 at 09:30:30AM -0700, Dan Carpenter wrote:
> Sparse finds that bug as well. ;)
>
> drivers/acpi/acpica/tbfadt.c:247:15: warning: incorrect type in assignment
> (different address spaces)
> drivers/acpi/acpica/tbfadt.c:247:15:expected struct acpi_table_header
> *table
>
On Sun, Sep 02, 2012 at 09:30:30AM -0700, Dan Carpenter wrote:
Sparse finds that bug as well. ;)
drivers/acpi/acpica/tbfadt.c:247:15: warning: incorrect type in assignment
(different address spaces)
drivers/acpi/acpica/tbfadt.c:247:15:expected struct acpi_table_header
*table
acpi_os_map_memory expects its return value to be in the __iomem address
space. Tag the variable we're using as such and use memcpy_fromio to
avoid further sparse warnings.
Signed-off-by: Kent Yoder k...@linux.vnet.ibm.com
---
drivers/char/tpm/tpm_acpi.c | 4 ++--
1 file changed, 2
On Thu, Aug 30, 2012 at 02:21:55PM -0500, Kent Yoder wrote:
> On Thu, Aug 30, 2012 at 10:45:56AM -0700, Dan Carpenter wrote:
> > On Thu, Aug 30, 2012 at 09:38:41AM -0500, Kent Yoder wrote:
> > > acpi_os_map_memory expects its return value to be in the __iomem address
> > > space. Cast it back
On Thu, Aug 30, 2012 at 02:21:55PM -0500, Kent Yoder wrote:
On Thu, Aug 30, 2012 at 10:45:56AM -0700, Dan Carpenter wrote:
On Thu, Aug 30, 2012 at 09:38:41AM -0500, Kent Yoder wrote:
acpi_os_map_memory expects its return value to be in the __iomem address
space. Cast it back later when
On Thu, Aug 30, 2012 at 10:45:56AM -0700, Dan Carpenter wrote:
> On Thu, Aug 30, 2012 at 09:38:41AM -0500, Kent Yoder wrote:
> > acpi_os_map_memory expects its return value to be in the __iomem address
> > space. Cast it back later when used in a memcpy to avoid the same sparse
> > warning there.
On Thu, Aug 30, 2012 at 09:38:41AM -0500, Kent Yoder wrote:
> acpi_os_map_memory expects its return value to be in the __iomem address
> space. Cast it back later when used in a memcpy to avoid the same sparse
> warning there.
>
> Signed-off-by: Kent Yoder
I can't download linux-next right now
acpi_os_map_memory expects its return value to be in the __iomem address
space. Cast it back later when used in a memcpy to avoid the same sparse
warning there.
Signed-off-by: Kent Yoder
---
drivers/char/tpm/tpm_acpi.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
acpi_os_map_memory expects its return value to be in the __iomem address
space. Cast it back later when used in a memcpy to avoid the same sparse
warning there.
Signed-off-by: Kent Yoder k...@linux.vnet.ibm.com
---
drivers/char/tpm/tpm_acpi.c |4 ++--
1 files changed, 2 insertions(+), 2
On Thu, Aug 30, 2012 at 09:38:41AM -0500, Kent Yoder wrote:
acpi_os_map_memory expects its return value to be in the __iomem address
space. Cast it back later when used in a memcpy to avoid the same sparse
warning there.
Signed-off-by: Kent Yoder k...@linux.vnet.ibm.com
I can't download
On Thu, Aug 30, 2012 at 10:45:56AM -0700, Dan Carpenter wrote:
On Thu, Aug 30, 2012 at 09:38:41AM -0500, Kent Yoder wrote:
acpi_os_map_memory expects its return value to be in the __iomem address
space. Cast it back later when used in a memcpy to avoid the same sparse
warning there.
14 matches
Mail list logo