From: Julian Gindi <juliangindi@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: Cleaning up a few return statements
Date: Tue, 05 May 2015 16:01:18 +0000 [thread overview]
Message-ID: <20150505160118.GA2280@Serenity.local> (raw)
In-Reply-To: <20150417204416.GA18202@rosebud>
On 05/04, Sudip Mukherjee wrote:
> On Sun, May 03, 2015 at 09:25:47PM +0200, Greg KH wrote:
> > On Fri, Apr 17, 2015 at 04:44:16PM -0400, Julian Gindi wrote:
> > > Signed-off-by: Julian Gindi <juliangindi@gmail.com>
> > >
> > >
> > > --
> > > 1.9.1
> >
> > This breaks the build, showing that you never even tested it :(
> sorry Greg, I should have buildtested after Julian has submitted the
> patch.
Apologies. Embarrasing mistake. I thought I tested, but was obviously
confused. Will fix and get everything working.
>
> regards
> sudip
prev parent reply other threads:[~2015-05-05 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 20:44 [PATCH] staging: sm750fb: Cleaning up a few return statements Julian Gindi
2015-05-03 19:25 ` Greg KH
2015-05-04 5:55 ` Sudip Mukherjee
2015-05-05 16:01 ` Julian Gindi [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=20150505160118.GA2280@Serenity.local \
--to=juliangindi@gmail.com \
--cc=linux-fbdev@vger.kernel.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).