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: Wed, 11 Mar 2015 08:43:09 +0100 [thread overview]
Message-ID: <20150311074309.GA5689@kroah.com> (raw)
In-Reply-To: <20150311072842.GA3550@sudip-PC>
On Wed, Mar 11, 2015 at 12:58:42PM +0530, Sudip Mukherjee wrote:
> On Tue, Mar 10, 2015 at 09:17:54PM +0100, Greg Kroah-Hartman wrote:
> > 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
> <snip>
> > >
> > > 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...
>
> thanks Greg for your patience and time to redo this patch. I saw you
> broke it into two - three different patches.
> But just one doubt, was your compiler showing any warning for the
> patch - "Staging: sm750fb: provide error path for
> hw_sm750le_setBLANK()" , commit id -
> e74ac550298ec4635cc32e99f966568a808fd370 . my compiler didnot show
> any warning for that.
> mine is gcc 4.7.3, is it time to update?
Yes it is, that's a really old version of gcc. Also please wrap your
email lines at 72 columns :)
> thanks again, and sorry that you had to do fix this. I should have
> made the patches in a more proper way.
Not a problem, it's part of the learning process.
greg k-h
next prev parent reply other threads:[~2015-03-11 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 17:16 [PATCH 0/6] staging: sm750fb: fixed all build warnings Sudip Mukherjee
2015-03-10 17:16 ` [PATCH 1/6] staging: sm750fb: remove unused functions Sudip Mukherjee
2015-03-10 17:16 ` [PATCH 2/6] staging: sm750fb: remove unused variables Sudip Mukherjee
2015-03-10 17:16 ` [PATCH 3/6] staging: sm750fb: correct function return Sudip Mukherjee
2015-03-10 17:16 ` [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
2015-03-11 7:28 ` Sudip Mukherjee
2015-03-11 7:43 ` Greg Kroah-Hartman [this message]
2015-03-10 17:16 ` [PATCH 5/6] staging: sm750fb: fix mixed declarations Sudip Mukherjee
2015-03-10 17:16 ` [PATCH 6/6] staging: sm750fb: correct integer comparison Sudip Mukherjee
2015-03-11 7:57 ` Dan Carpenter
2015-03-11 8:55 ` 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=20150311074309.GA5689@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