All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ico Doornekamp <ico@pruts.nl>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: CAN libpcap capture endianess
Date: Wed, 11 May 2016 19:01:58 +0200	[thread overview]
Message-ID: <1462986044-sup-1378@pruts.nl> (raw)
In-Reply-To: <573332DA.7070400@hartkopp.net>

* On 2016-05-11 15:25:46 +0200, Oliver Hartkopp wrote:
 
> When my posted patch does not have an effect it may be worth looking at 
> the differences of the selected qdiscs (noqueue/pfifo).

No difference with the patch, I'll look into the qdiscs

> Hm - no.

Sorry, my wrong - I missed the part where you said 'I forgot slcan.c', and just
took a look at the patch in the link.

-- 
:wq
^X^Cy^K^X^C^C^C^C

      reply	other threads:[~2016-05-11 17:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 17:42 CAN libpcap capture endianess Ico
2013-09-11 18:22 ` Marc Kleine-Budde
2013-09-11 18:30   ` Ico Doornekamp
2013-09-11 18:38     ` Marc Kleine-Budde
2013-09-11 18:53       ` Ico Doornekamp
2013-09-11 19:22         ` Oliver Hartkopp
2013-09-11 19:17       ` Oliver Hartkopp
2013-09-11 19:34         ` Marc Kleine-Budde
2013-09-11 19:37 ` Marc Kleine-Budde
2013-09-11 20:05   ` Ico Doornekamp
2013-09-11 20:11     ` Marc Kleine-Budde
2013-09-12  6:52       ` Ico Doornekamp
2013-09-12  8:00         ` Marc Kleine-Budde
2013-09-12  8:47           ` Ico Doornekamp
2013-09-12  8:52             ` Marc Kleine-Budde
2013-09-12  9:09               ` Ico Doornekamp
2013-09-12  9:13                 ` Marc Kleine-Budde
2013-09-12  9:31                   ` Ico Doornekamp
2016-05-10 19:25 ` Ico Doornekamp
2016-05-11  7:40   ` Oliver Hartkopp
     [not found]     ` <1462952665-sup-1016@pruts.nl>
2016-05-11  8:17       ` Oliver Hartkopp
2016-05-11 12:28         ` Ico Doornekamp
2016-05-11 13:25           ` Oliver Hartkopp
2016-05-11 17:01             ` Ico Doornekamp [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=1462986044-sup-1378@pruts.nl \
    --to=ico@pruts.nl \
    --cc=linux-can@vger.kernel.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 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.