From: Fabio Baltieri <fabio.baltieri@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org, Kurt Van Dijck <kurt.van.dijck@eia.be>,
Wolfgang Grandegger <wg@grandegger.com>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Bernd Krumboeck <b.krumboeck@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/10] tx/rx LED trigger support
Date: Tue, 22 Jan 2013 23:53:22 +0100 [thread overview]
Message-ID: <20130122225322.GA13211@balto.lan> (raw)
In-Reply-To: <50FF0ACB.6000702@pengutronix.de>
Hi Marc,
On Tue, Jan 22, 2013 at 10:55:23PM +0100, Marc Kleine-Budde wrote:
> On 01/15/2013 09:41 PM, Marc Kleine-Budde wrote:
>
> I've tweaked some comments in some of these patches, too.
Of course it looks fine to me. Networking style block comment check in
checkpatch was not in place when I originally wrote this code! :-)
Thanks,
Fabio
--
Fabio Baltieri
prev parent reply other threads:[~2013-01-22 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 17:50 [PATCH v2 00/10] tx/rx LED trigger support Fabio Baltieri
2012-12-18 17:50 ` [PATCH 01/10] can: add " Fabio Baltieri
2012-12-18 17:50 ` [PATCH 02/10] can: export a safe netdev_priv wrapper for candev Fabio Baltieri
2012-12-18 17:50 ` [PATCH 03/10] can: rename LED trigger name on netdev renames Fabio Baltieri
2012-12-18 17:50 ` [PATCH 04/10] can: flexcan: add LED trigger support Fabio Baltieri
2012-12-18 17:50 ` [PATCH 05/10] can: at91_can: " Fabio Baltieri
2012-12-18 17:51 ` [PATCH 06/10] can: ti_hecc: " Fabio Baltieri
2012-12-18 17:51 ` [PATCH 07/10] can: c_can: " Fabio Baltieri
2012-12-18 17:51 ` [PATCH 08/10] can: mcp251x: " Fabio Baltieri
2012-12-18 17:51 ` [PATCH 09/10] can: sja1000: " Fabio Baltieri
2012-12-18 17:51 ` [PATCH 10/10] can: usb_8dev: " Fabio Baltieri
2013-01-15 20:41 ` [PATCH v2 00/10] tx/rx " Marc Kleine-Budde
2013-01-22 21:39 ` Marc Kleine-Budde
2013-01-22 21:55 ` Marc Kleine-Budde
2013-01-22 22:53 ` Fabio Baltieri [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=20130122225322.GA13211@balto.lan \
--to=fabio.baltieri@gmail.com \
--cc=b.krumboeck@gmail.com \
--cc=kurt.van.dijck@eia.be \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.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).