Linux CAN drivers development
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Prabhakar Lad <prabhakar.csengg@gmail.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [Gitorious] Activity: prabhakar requested a merge of prab...
Date: Tue, 24 Jun 2014 13:11:03 +0200	[thread overview]
Message-ID: <53A95CC7.5000008@pengutronix.de> (raw)
In-Reply-To: <CA+V-a8tcsgj1h+Qu0OSXGEoXvpbm7r0itQTRnmDpQgXiz1t-PA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2139 bytes --]

On 06/24/2014 01:06 PM, Prabhakar Lad wrote:
> Hi
> 
> On Mon, Jun 23, 2014 at 5:46 PM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>> On 06/23/2014 06:30 PM, Oliver Hartkopp wrote:
>>> On 23.06.2014 18:22, Marc Kleine-Budde wrote:
>>>> On 06/23/2014 06:12 PM, Oliver Hartkopp wrote:
>>>>> Hi Prabhakar,
>>>>>
>>>>> thanks for your patch.
>>>>>
>>>>> Can you please send it with git send-email to the mailing list for a review?
>>>>>
>>>>> Additionally:
>>>>>
>>>>> Does this patch introduce any backward compatibility restrictions (e.g. you
>>>>> need at least the includes from 2.6.14+ to build candump ...).
>>>>
>>>> When was CAN support added to the linux kernel? :)
>>>
>>> I know that you would detect this joke ;-)
>>> Btw. I backported SocketCAN to 2.6.13 - so my question is not totally
>>> brain-damaged when talking about the can-utils which are not sticking to a
>>> specific kernel version.
>>
>> I was assuming that there was a certain seriousness in your statement :D
>>
>> Do you mean the inclusion of "sched.h"? I think this comes from the
>> glibc. However, we can add autotool support to detect this.
>>
>>>>> You only provide to configure a value for SCHED_RR.
>>>>> Does it make sense to provide other scheduling policies too?
>>>>
>>>> I would use chrt to start the tool, if I need non standard scheduling
>>>> policies.
>>>
>>> But then you would like to specifiy the scheduling policy??
>>
>> You can use chrt to start another program with different scheduling
>> policies, it's like nice, but with more functionality. See man page of
>> chrt for more information.
>>
> What do you suggest to go with the patch or just use chrt ?

From my point of view candump is a debugging tool anyways, using it
together with chrt makes sense. Do you have a good argument why not to
use chrt?

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: 242 bytes --]

  reply	other threads:[~2014-06-24 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53a829dc98811_78d23ff48250bea851769@ratt.gitorious.c.bitbit.net.mail>
2014-06-23 16:12 ` [Gitorious] Activity: prabhakar requested a merge of prab Oliver Hartkopp
2014-06-23 16:22   ` Marc Kleine-Budde
2014-06-23 16:30     ` Oliver Hartkopp
2014-06-23 16:46       ` Marc Kleine-Budde
2014-06-24 11:06         ` Prabhakar Lad
2014-06-24 11:11           ` Marc Kleine-Budde [this message]
2014-06-24 13:50             ` Prabhakar Lad

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=53A95CC7.5000008@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=prabhakar.csengg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox