linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] staging: sm750fb: correct incompatible pointer type
Date: Tue, 10 Mar 2015 20:17:54 +0000	[thread overview]
Message-ID: <20150310201754.GA8122@kroah.com> (raw)
In-Reply-To: <20150310201100.GA17629@kroah.com>

On Tue, Mar 10, 2015 at 09:11:00PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 10, 2015 at 10:46:55PM +0530, Sudip Mukherjee wrote:
> > we were getting build warnings about assignment of incompatible
> > pointer types. some of the function definitions were having wrong
> > return type or arguments.
> > 
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> > ---
> >  drivers/staging/sm750fb/sm750.h       | 11 ++++++-----
> >  drivers/staging/sm750fb/sm750_accel.c |  4 ++--
> >  drivers/staging/sm750fb/sm750_accel.h |  4 ++--
> >  3 files changed, 10 insertions(+), 9 deletions(-)
> > 
> > diff --git a/drivers/staging/sm750fb/sm750.h b/drivers/staging/sm750fb/sm750.h
> > index d39968c..edb955a 100644
> > --- a/drivers/staging/sm750fb/sm750.h
> > +++ b/drivers/staging/sm750fb/sm750.h
> > @@ -23,7 +23,7 @@ struct lynx_accel{
> >  	volatile unsigned char __iomem * dpPortBase;
> >  
> >  	/* function fointers */
> > -	int (*de_init)(struct lynx_accel *);
> > +	void (*de_init)(struct lynx_accel *);
> 
> That's ok, but:
> 
> >  
> >  	int (*de_wait)(void);/* see if hardware ready to work */
> >  
> > @@ -34,8 +34,8 @@ struct lynx_accel{
> >  						u32,u32,u32,u32,
> >  						u32,u32,u32,u32);
> >  
> > -	int (*de_imageblit)(struct lynx_accel *,const char *,u32,u32,u32,
> > -						u32,u32,u32,u32,u32,u32,u32,u32,u32);
> > +	int (*de_imageblit)(struct lynx_accel *, const char *, u32, u32, u32,
> > +			    u32, u32, u32, u32, u32, u32, u32, u32, u32);
> >  
> 
> 
> This isn't fixing an error.
> 
> >  };
> >  
> > @@ -120,8 +120,9 @@ struct lynxfb_crtc{
> >  	int(*proc_setColReg)(struct lynxfb_crtc*,ushort,ushort,ushort,ushort);
> >  	void (*clear)(struct lynxfb_crtc*);
> >          /* pan display */
> > -        int(*proc_panDisplay)(struct lynxfb_crtc*, struct fb_var_screeninfo*,
> > -                struct fb_info*);
> > +	int (*proc_panDisplay)(struct lynxfb_crtc*,
> > +			       const struct fb_var_screeninfo*,
> > +			       const struct fb_info*);
> 
> That's a nice cleanup, but it's not even the correct cleanup.

Oops, sorry, it is the correct cleanup, I was looking at the '*'
placement, not the const part.

but the patch needs to be redone, I'll just go fix up the build warnings
for now...

greg k-h

  reply	other threads:[~2015-03-10 20:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 17:28 [PATCH 0/6] staging: sm750fb: fixed all build warnings Sudip Mukherjee
2015-03-10 17:28 ` [PATCH 1/6] staging: sm750fb: remove unused functions Sudip Mukherjee
2015-03-10 17:28 ` [PATCH 2/6] staging: sm750fb: remove unused variables Sudip Mukherjee
2015-03-10 17:28 ` [PATCH 3/6] staging: sm750fb: correct function return Sudip Mukherjee
2015-03-10 17:28 ` [PATCH 4/6] staging: sm750fb: correct incompatible pointer type Sudip Mukherjee
2015-03-10 20:11   ` Greg Kroah-Hartman
2015-03-10 20:17     ` Greg Kroah-Hartman [this message]
2015-03-11  7:40       ` Sudip Mukherjee
2015-03-11  7:43         ` Greg Kroah-Hartman
2015-03-10 17:28 ` [PATCH 5/6] staging: sm750fb: fix mixed declarations Sudip Mukherjee
2015-03-10 17:28 ` [PATCH 6/6] staging: sm750fb: correct integer comparison Sudip Mukherjee
2015-03-11  7:57   ` Dan Carpenter
2015-03-11  8:56     ` Sudip Mukherjee
2015-03-10 20:13 ` [PATCH 0/6] staging: sm750fb: fixed all build warnings Greg Kroah-Hartman

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=20150310201754.GA8122@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).