From: Greg KH <gregkh@suse.de>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Bill Pemberton <wfp5p@virginia.edu>,
Arnaud Patard <apatard@mandriva.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Huang Weiyi <weiyi.huang@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] staging: xgifb: Fix compile warning
Date: Sat, 4 Sep 2010 23:23:53 -0700 [thread overview]
Message-ID: <20100905062353.GA18329@suse.de> (raw)
In-Reply-To: <1283641607.9641.4.camel@lenovo>
On Sat, Sep 04, 2010 at 07:06:47PM -0400, Javier Martinez Canillas wrote:
> Hello, In today linux-next I got a some compile warnings with the staging/xgifb driver. This is the first of a 4 patchset that fix all the issues.
>
> The patches are:
>
> [PATCH 1/4] staging: xgifb: Fix compile warning
> [PATCH 2/4] staging: xgifb: Add compilation conditionals
> [PATCH 3/4] staging: xgifb: Removes unused variable
> [PATCH 4/4] staging: xgifb: Init uninitialized variables and fix some style issues
>
> Thanks a lot.
>
> Signed-off-by: Javier Martinez Canillas <martinez.javier@gmail.com>
> ---
> drivers/staging/xgifb/XGI_main_26.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/staging/xgifb/XGI_main_26.c b/drivers/staging/xgifb/XGI_main_26.c
> index 7cd3e95..3c80191 100644
> --- a/drivers/staging/xgifb/XGI_main_26.c
> +++ b/drivers/staging/xgifb/XGI_main_26.c
> @@ -3418,7 +3418,7 @@ static int __devinit xgifb_probe(struct pci_dev *pdev,
> XGIfb_registered = 1;
>
> printk(KERN_INFO "XGIfb: Installed XGIFB_GET_INFO ioctl (%lx)\n",
> - XGIFB_GET_INFO);
> + (unsigned long)XGIFB_GET_INFO);
No, you should use %p instead.
Also, you don't spam the kernel log for assigning an ioctl function
pointer, that's just looney...
thanks,
greg k-h
prev parent reply other threads:[~2010-09-05 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 23:06 [PATCH 1/4] staging: xgifb: Fix compile warning Javier Martinez Canillas
2010-09-05 6:23 ` Greg KH [this message]
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=20100905062353.GA18329@suse.de \
--to=gregkh@suse.de \
--cc=apatard@mandriva.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=weiyi.huang@gmail.com \
--cc=wfp5p@virginia.edu \
/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