From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Brian Thorne <hardbyte@gmail.com>,
Daniele Venzano <linux@brownhat.org>,
Andre Naujoks <nautsch2@gmail.com>
Subject: Re: [can-next] can: add broadcast manager documentation
Date: Thu, 31 Oct 2013 20:55:01 +0100 [thread overview]
Message-ID: <5272B595.3090102@pengutronix.de> (raw)
In-Reply-To: <52625C90.6030508@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]
On 10/19/2013 12:18 PM, Oliver Hartkopp wrote:
> Signed-off-by: Brian Thorne <hardbyte@gmail.com>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> CC: Daniele Venzano <linux@brownhat.org>
> CC: Andre Naujoks <nautsch2@gmail.com>
>
> ---
>
> Hi all,
>
> after the latest attempt from Brian i reworked a CAN BCM documentation based
> on Brians patch: http://marc.info/?l=linux-can&m=138119382015496&w=2
>
> It's a bit shorter than the original documentation that has been translated
> and reworked by Daniele here: http://brownhat.org/docs/socketcan.html
>
> I hope, i was able to catch all the provided functionalities and typos :-)
>
> Thanks for your support and patience.
I added credits you listed here to the patch's description, because
these mentioned won't get into the kernel and some maintainers and me
think that a patch shouldn't have an empty description :)
The patch description now looks like this:
---
can: add broadcast manager documentation
This patch adds documentation about the broadcast manager. It's based on Brian
Thorne's initial patch http://marc.info/?l=linux-can&m=138119382015496&w=2 and
Daniele Venzano's work http://brownhat.org/docs/socketcan.html .
Signed-off-by: Brian Thorne <hardbyte@gmail.com>
Cc: Daniele Venzano <linux@brownhat.org>
Cc: Andre Naujoks <nautsch2@gmail.com>
Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
----
Any objections?
Marc
--
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: 259 bytes --]
next prev parent reply other threads:[~2013-10-31 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 10:18 [can-next] can: add broadcast manager documentation Oliver Hartkopp
2013-10-31 19:55 ` Marc Kleine-Budde [this message]
2013-10-31 19:57 ` Oliver Hartkopp
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=5272B595.3090102@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=hardbyte@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux@brownhat.org \
--cc=nautsch2@gmail.com \
--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.