From: Dan Carpenter <error27@gmail.com>
To: Marek Belisko <marek.belisko@open-nandra.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/11] staging: ft1000: Various coding style cleanups.
Date: Tue, 25 Jan 2011 16:32:40 +0300 [thread overview]
Message-ID: <20110125133240.GH2721@bicker> (raw)
In-Reply-To: <1295960706-15667-1-git-send-email-marek.belisko@open-nandra.com>
Looks good.
Reviewed-by: Dan Carpenter <error27@gmail.com>
regards,
dan carpenter
prev parent reply other threads:[~2011-01-25 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 13:04 [PATCH v2 00/11] staging: ft1000: Various coding style cleanups Marek Belisko
2011-01-25 13:04 ` [PATCH v2 01/11] staging: ft1000: Remove dead code Marek Belisko
2011-01-25 13:04 ` [PATCH v2 02/11] staging: ft1000: Fix coding style in check_usb_db() function Marek Belisko
2011-01-25 13:04 ` [PATCH v2 03/11] staging: ft1000: Fix coding style in put_handshake() function Marek Belisko
2011-01-25 13:04 ` [PATCH v2 04/11] staging: ft1000: Fix coding style in get_handshake_usb() function Marek Belisko
2011-01-25 13:05 ` [PATCH v2 05/11] staging: ft1000: Fix coding style in put_handshake_usb() function Marek Belisko
2011-01-25 13:05 ` [PATCH v2 06/11] staging: ft1000: Fix coding style in get_request_type() function Marek Belisko
2011-01-25 13:05 ` [PATCH v2 07/11] staging: ft1000: Fix coding style in get_request_type_usb() function Marek Belisko
2011-01-25 13:05 ` [PATCH v2 08/11] staging: ft1000: Fix coding style in get_request_value() function Marek Belisko
2011-01-25 13:05 ` [PATCH v2 09/11] staging: ft1000: Fix coding style in put_request_value() function Marek Belisko
2011-01-25 15:23 ` Alexey Dobriyan
2011-01-25 13:05 ` [PATCH v2 10/11] staging: ft1000: Fix coding style in hdr_checksum() function Marek Belisko
2011-01-25 13:05 ` [PATCH v2 11/11] staging: ft1000: Fix coding style in get_handshake() function Marek Belisko
2011-01-25 13:32 ` Dan Carpenter [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=20110125133240.GH2721@bicker \
--to=error27@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@open-nandra.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.