From: Jonathan Corbet <corbet@lwn.net>
To: Stefan Tatschner <rumpelsepp@sevenbyte.org>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org
Subject: Re: [PATCH] can-doc: Add hint about getting timestamps
Date: Thu, 10 Dec 2015 11:29:24 -0700 [thread overview]
Message-ID: <20151210112924.4e8585f0@lwn.net> (raw)
In-Reply-To: <1448373989-7241-1-git-send-email-rumpelsepp@sevenbyte.org>
On Tue, 24 Nov 2015 15:06:29 +0100
Stefan Tatschner <rumpelsepp@sevenbyte.org> wrote:
> This patch adds a hint about how to get timestamps of received
> CAN frames with ioctl(2). This hint has been applied to the
> former SocketCAN Documentation, but it got lost during mainlining
> the first bits and pieces to linux kernel.
Applied to the docs tree, thanks.
jon
prev parent reply other threads:[~2015-12-10 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 13:07 SocketCAN timestamps Stefan Tatschner
2015-11-24 13:42 ` Marc Kleine-Budde
2015-11-24 14:06 ` [PATCH] can-doc: Add hint about getting timestamps Stefan Tatschner
2015-12-08 10:07 ` Stefan Tatschner
2015-12-10 18:29 ` Jonathan Corbet [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=20151210112924.4e8585f0@lwn.net \
--to=corbet@lwn.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=rumpelsepp@sevenbyte.org \
--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 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).