From: Aldo Iljazi <mail@aldo.io>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: marek.belisko@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: ft1000: ft1000_download: fixed coding style issues
Date: Tue, 12 Nov 2013 09:48:19 +0200 [thread overview]
Message-ID: <20131112074819.GA19657@elementary> (raw)
In-Reply-To: <20131112002709.GA7709@kroah.com>
Greg KH wrote:
> On Sun, Nov 10, 2013 at 03:44:20PM +0200, Aldo Iljazi wrote:
> > Fixed the following coding style issues:
>
> Note that I added the filename to the Subject:, please do so in the
> future to make it easier to see what exactly you are changing.
You are right. I'll do that.
--
Aldo Iljazi
prev parent reply other threads:[~2013-11-12 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 13:44 [PATCH] Staging: ft1000: fixed coding style issues Aldo Iljazi
2013-11-12 0:27 ` [PATCH] Staging: ft1000: ft1000_download: " Greg KH
2013-11-12 7:48 ` Aldo Iljazi [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=20131112074819.GA19657@elementary \
--to=mail@aldo.io \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@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).