From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Senna Tschudin <peter.senna@gmail.com>
Cc: alan@linux.intel.com, dan.carpenter@oracle.com,
geert@linux-m68k.org, devel@driverdev.osuosl.org,
jun.j.tian@intel.com, linux-kernel@vger.kernel.org,
schwab@linux-m68k.org, garret.kelly@gmail.com,
octavian.purdila@intel.com, nnk@google.com
Subject: Re: [PATCH V5] staging: goldfish: Fix pointer cast for 32 bits
Date: Sat, 9 May 2015 18:24:04 +0200 [thread overview]
Message-ID: <20150509162404.GA14324@kroah.com> (raw)
In-Reply-To: <1430745078-15969-1-git-send-email-peter.senna@gmail.com>
On Mon, May 04, 2015 at 03:11:18PM +0200, Peter Senna Tschudin wrote:
> As the first argument of gf_write64() was of type unsigned long, and as
> some calls to gf_write64() were casting the first argument from void *
> to u64 the compiler and/or sparse were printing warnings for casts of
> wrong sizes when compiling for i386.
>
> This patch changes the type of the first argument of gf_write64() to
> void *, and update calls to the function. This change fixed the
> warnings and allowed to remove casts from 6 calls to gf_write64().
>
> In addition gf_write64() was renamed to gf_write_ptr() as the name was
> misleading because it only writes 32 bits on 32 bit systems.
>
> gf_write_dma_addr() was added to handle dma_addr_t values which is
> used at drivers/staging/goldfish/goldfish_audio.c.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
> ---
> Tested by compilation only for x86 and for x86_64.
This adds two build warnings:
drivers/tty/goldfish.c: In function ‘goldfish_tty_do_write’:
drivers/tty/goldfish.c:62:15: warning: passing argument 1 of ‘gf_write_ptr’ discards ‘const’ qualifier from pointer target type
gf_write_ptr(buf, base + GOLDFISH_TTY_DATA_PTR,
^
In file included from drivers/tty/goldfish.c:24:0:
include/linux/goldfish.h:6:20: note: expected ‘void *’ but argument is of type ‘const char *’
static inline void gf_write_ptr(void *ptr, void __iomem *portl,
^
So I can't take this. Please fix up and resend, and always test build your
patches...
thanks,
greg k-h
next prev parent reply other threads:[~2015-05-09 16:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 9:26 [PATCH] Fix pointer cast for 32 bits arch Peter Senna Tschudin
2015-04-12 13:05 ` Geert Uytterhoeven
2015-04-12 13:48 ` Peter Senna Tschudin
2015-04-12 15:38 ` Geert Uytterhoeven
2015-04-12 18:14 ` Joe Perches
2015-04-12 19:06 ` Geert Uytterhoeven
2015-04-13 11:14 ` Peter Senna Tschudin
2015-04-13 11:21 ` Geert Uytterhoeven
2015-04-13 11:25 ` Peter Senna Tschudin
2015-04-13 12:31 ` Dan Carpenter
2015-04-16 13:39 ` [PATCH V4] " Peter Senna Tschudin
2015-04-16 16:14 ` Geert Uytterhoeven
2015-04-16 17:01 ` Dan Carpenter
2015-04-16 17:05 ` Alan Cox
2015-04-16 18:36 ` Peter Senna Tschudin
2015-05-03 18:32 ` Greg Kroah-Hartman
2015-05-04 13:11 ` [PATCH V5] staging: goldfish: Fix pointer cast for 32 bits Peter Senna Tschudin
2015-05-04 13:34 ` Dan Carpenter
2015-05-09 16:24 ` Greg KH [this message]
2015-05-19 9:44 ` [PATCH V6] " Peter Senna Tschudin
2015-04-17 8:11 ` [PATCH V4] Fix pointer cast for 32 bits arch Dan Carpenter
2015-04-17 8:20 ` Dan Carpenter
2015-04-17 13:31 ` Alan Cox
2015-04-17 13:59 ` Dan Carpenter
2015-04-17 14:10 ` Alan Cox
2015-04-18 13:34 ` Peter Senna Tschudin
2015-04-18 13:59 ` Dan Carpenter
2015-04-13 9:10 ` [PATCH] " Dan Carpenter
2015-04-13 9:16 ` Peter Senna Tschudin
2015-04-13 9:21 ` 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=20150509162404.GA14324@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=garret.kelly@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jun.j.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nnk@google.com \
--cc=octavian.purdila@intel.com \
--cc=peter.senna@gmail.com \
--cc=schwab@linux-m68k.org \
/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;
as well as URLs for NNTP newsgroup(s).