From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"Heinz-Jürgen Oertel" <oe@port.de>
Subject: Re: [PATCH] can: update documentation wording error frames -> error messages
Date: Tue, 08 May 2012 22:38:25 +0200 [thread overview]
Message-ID: <4FA98441.8090308@pengutronix.de> (raw)
In-Reply-To: <4FA98011.3020600@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On 05/08/2012 10:20 PM, Oliver Hartkopp wrote:
> As Heinz-Juergen Oertel pointed out 'CAN error frames' are a already defined
> term for the CAN protocol violation indication on the wire.
>
> To avoid confusion with the error messages created by CAN drivers available
> via CAN RAW sockets update the documentation and change the naming from
> 'error frames' to 'error messages' or 'error message frames'.
>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Sounds reasonable. Heinz-Jürgen, can I add your Acked-by: to this patch?
It means that you've read the patch and think this is a good change.
Marc
P.S.: Oliver, try to use: "git send-email", it much easier for you to
send patches than to copy/paste it to thunderbird.
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-05-08 20:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 11:42 [PATCH] MAINTAINERS: can: the mailinglist moved to vger.kernel.org Marc Kleine-Budde
2011-10-13 20:17 ` Oliver Hartkopp
2011-11-02 20:55 ` [PATCH] MAINTAINERS: Add can-gw include to maintained files Oliver Hartkopp
2011-11-03 22:12 ` David Miller
2012-02-14 19:27 ` [PATCH] can: sja1000 fix isr hang when hw is unplugged under load Oliver Hartkopp
2012-02-15 16:51 ` [PATCH v2] " Oliver Hartkopp
2012-02-17 20:27 ` Marc Kleine-Budde
2012-02-18 14:19 ` Oliver Hartkopp
2012-02-18 17:00 ` Marc Kleine-Budde
2012-02-20 11:02 ` Marc Kleine-Budde
2012-02-21 8:07 ` Oliver Hartkopp
2012-02-21 9:03 ` Marc Kleine-Budde
2012-02-18 14:33 ` Wolfgang Grandegger
2012-02-18 15:34 ` Oliver Hartkopp
2012-02-18 16:44 ` Wolfgang Grandegger
2012-02-18 17:00 ` Marc Kleine-Budde
2012-02-18 17:13 ` Wolfgang Grandegger
2012-03-25 6:43 ` [PATCH] iwlwifi: fix unused variable warning Oliver Hartkopp
2012-03-26 1:49 ` Guy, Wey-Yi
2012-04-03 19:56 ` [PATCH RFC] can: add hash table for single EFF id filter list Oliver Hartkopp
2012-05-08 20:20 ` [PATCH] can: update documentation wording error frames -> error messages Oliver Hartkopp
2012-05-08 20:38 ` Marc Kleine-Budde [this message]
2012-05-09 17:09 ` Heinz-Jürgen Oertel
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=4FA98441.8090308@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=oe@port.de \
--cc=socketcan@hartkopp.net \
/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.