From: Othmar Pasteka <pasteka@kabsi.at>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
sudip@vectorindia.org, greg@kroah.com,
devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: sm750fb: add spaces around operator
Date: Sun, 08 Nov 2015 07:33:16 +0000 [thread overview]
Message-ID: <20151108073315.GA22116@tron.local> (raw)
In-Reply-To: <20151108063508.GM18797@mwanda>
On Sun, Nov 08, 2015 at 09:35:08AM +0300, Dan Carpenter wrote:
> If it's a one line fix then just send it as a single patch.
It was two things, hence I made it a two-parter.
Should I send a new version or is it a note for next time?
Thanks,
Othmar Pasteka
next prev parent reply other threads:[~2015-11-08 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 0:43 [PATCH 1/2] staging: sm750fb: move opening brace to previous line Othmar Pasteka
2015-11-08 0:43 ` [PATCH 2/2] staging: sm750fb: add spaces around operator Othmar Pasteka
2015-11-08 6:35 ` Dan Carpenter
2015-11-08 7:33 ` Othmar Pasteka [this message]
2015-11-08 8:17 ` 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=20151108073315.GA22116@tron.local \
--to=pasteka@kabsi.at \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudip@vectorindia.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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).