From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>, prabhakar.csengg@gmail.com
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [Gitorious] Activity: prabhakar requested a merge of prab...
Date: Mon, 23 Jun 2014 18:22:29 +0200 [thread overview]
Message-ID: <53A85445.8070400@pengutronix.de> (raw)
In-Reply-To: <53A851DC.2060801@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
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? :)
> 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.
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 --]
next prev parent reply other threads:[~2014-06-23 16:22 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 [this message]
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
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=53A85445.8070400@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 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.