From: Julian Andres Klode <jak@jak-linux.org>
To: Autif Khan <tekxtc@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
edwin_rong <edwin_rong@realsil.com.cn>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Fixed a coding style issue
Date: Mon, 30 Jan 2012 21:17:49 +0100 [thread overview]
Message-ID: <20120130201749.GA21240@jak-linux.org> (raw)
In-Reply-To: <1327948562-3548-1-git-send-email-tekxtc@gmail.com>
On Mon, Jan 30, 2012 at 01:36:02PM -0500, Autif Khan wrote:
> Subject: [PATCH 2/2] Fixed a coding style issue
Numbering gone wrong (you have a 1/1 and a 2/2, while you
probably should have 1/2 and 2/2)? And the title for this
and the previous email are also fairly generic, they don't
even mention which driver is modified.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
prev parent reply other threads:[~2012-01-30 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 18:36 [PATCH 2/2] Fixed a coding style issue Autif Khan
2012-01-30 20:17 ` Julian Andres Klode [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=20120130201749.GA21240@jak-linux.org \
--to=jak@jak-linux.org \
--cc=devel@driverdev.osuosl.org \
--cc=edwin_rong@realsil.com.cn \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tekxtc@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).