From: Tony Cho <tony.cho@atmel.com>
To: <janani.rvchndrn@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, <glen.lee@atmel.com>,
<leo.kim@atmel.com>, <chris.park@atmel.com>,
<linux-wireless@vger.kernel.org>, <devel@driverdev.osuosl.org>
Subject: whitespace error in some of commits
Date: Tue, 16 Feb 2016 15:47:00 +0900 [thread overview]
Message-ID: <56C2C5E4.9080006@atmel.com> (raw)
Hi Janani,
I can find the whitespace errors in your commits which is already accepted in staging-testing branch.
The commit number is c611d48e65e25af2dc0176e9ac135116095ed03d and c611d48e65e25af2dc0176e9ac135116095ed03d.
I don't know why I couldn't find your patch emails from the community. Please cc the linux-wireless and devel.
Would you fix these patch or I can make it if you don't mind.
Thanks,
Tony.
next reply other threads:[~2016-02-16 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 6:47 Tony Cho [this message]
2016-02-16 7:07 ` whitespace error in some of commits Tony Cho
2016-02-16 16:11 ` Greg KH
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=56C2C5E4.9080006@atmel.com \
--to=tony.cho@atmel.com \
--cc=chris.park@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=glen.lee@atmel.com \
--cc=gregkh@linuxfoundation.org \
--cc=janani.rvchndrn@gmail.com \
--cc=leo.kim@atmel.com \
--cc=linux-wireless@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).