From: David Miller <davem@davemloft.net>
To: flexray4linux@scriptkiller.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] FlexRay: Allocate numbers for FlexRay communication
Date: Thu, 30 Apr 2009 09:50:26 -0700 (PDT) [thread overview]
Message-ID: <20090430.095026.184167467.davem@davemloft.net> (raw)
In-Reply-To: <20090430163825.GX13310@m58s01.vlinux.de>
From: Michael Arndt <flexray4linux@scriptkiller.de>
Date: Thu, 30 Apr 2009 18:38:26 +0200
> Further code including the FlexRay core, raw sockets and
> examples will soon be posted on a yet-to-be-created project site.
These definitions can be added when you are able to get FlexRay into
the upstream sources.
And no sooner.
This policy is applied equally to everyone, so please don't argue
it.
next prev parent reply other threads:[~2009-04-30 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 16:38 [PATCH] FlexRay: Allocate numbers for FlexRay communication Michael Arndt
2009-04-30 16:50 ` David Miller [this message]
2009-04-30 17:28 ` Oliver Hartkopp
2009-05-02 16:32 ` Michael Arndt
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=20090430.095026.184167467.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=flexray4linux@scriptkiller.de \
--cc=netdev@vger.kernel.org \
/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).