From: Wolfgang Grandegger <wg@grandegger.com>
To: Steffen Rose <ro@emtas.de>
Cc: linux-can@vger.kernel.org,
Oliver Hartkopp <socketcan@hartkopp.net>,
Gabriel Manriquez <gmanriquez@wegmannusa.com>
Subject: Re: socketCan build fails
Date: Mon, 27 Feb 2012 10:32:32 +0100 [thread overview]
Message-ID: <4F4B4DB0.4060400@grandegger.com> (raw)
In-Reply-To: <9642069.LSMGlbII5g@lisa>
Hi Steffen,
On 02/27/2012 10:12 AM, Steffen Rose wrote:
> Hi,
>
>> The content of the kernel/2.6 directory is mainly needed for older Kernels
>> that do not have SocketCAN support (which was introduced in 2.6.25).
>
> differ the kernel socketCAN path from our used socketCAN?
Yes, if "our used socketCAN" means the out-of-tree "SocketCAN
repository" (formerly at BerliOS and now at gitorious.rog).
> Of course, I know, this both are different repositories. But I was the meaning,
> that at the first the changes comes in our repository and later our patches are
> copied to the kernel.
Unfortunately, that's not the case. The main focus is on providing
support for the mainline kernel. The intention is that patches/fixes are
backported from the kernel tree but also that did not always happen.
Both trees are not in full sync, sorry.
> Additional question:
> Are there a Kernel list with information, which socketCAN feature is included
> (e.g. 3.2 - gateway functionality)?
"$ git log drivers/net/can" should provide that information.
> Is there a "TAG" in our repository to see, which software state was copied to
> which kernel version?
No, see above.
Wolfgang.
prev parent reply other threads:[~2012-02-27 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 15:02 socketCan build fails Gabriel Manriquez
2012-02-23 17:21 ` Oliver Hartkopp
2012-02-23 17:33 ` Gabriel Manriquez
2012-02-23 17:48 ` Oliver Hartkopp
2012-02-24 13:46 ` Gabriel Manriquez
2012-02-27 9:12 ` Steffen Rose
2012-02-27 9:32 ` Wolfgang Grandegger [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=4F4B4DB0.4060400@grandegger.com \
--to=wg@grandegger.com \
--cc=gmanriquez@wegmannusa.com \
--cc=linux-can@vger.kernel.org \
--cc=ro@emtas.de \
--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).