From: martinez.javier@gmail.com (Javier Martinez Canillas)
To: kernelnewbies@lists.kernelnewbies.org
Subject: wrapfs sources
Date: Thu, 5 Apr 2012 12:59:35 +0200 [thread overview]
Message-ID: <CAAwP0s3gpZgbhPFUsiMV1P2ZEp+ekV7+AsKU8hOVy-ux7gavTQ@mail.gmail.com> (raw)
In-Reply-To: <CA+CftcGp+6-4o40muG-xR9FMZJJH32aFMOLafip1P8ZrrNiN2w@mail.gmail.com>
On Wed, Apr 4, 2012 at 6:32 AM, V.Ravikumar
<ravikumar.vallabhu@gmail.com> wrote:
> Hi all,
>
> Could some body let me know wrapfs sources which is compatible to Linux
> 2.6.18 kernel sources.
>
> I tried to get sources using google search , but all are compatible with
> latest kernel sources.
>
> Thanks & Regards,
> Ravi
>
Hi Ravi,
If I were you I would clone from
git://git.fsl.cs.sunysb.edu/wrapfs-latest.git and checkout from a
commitid that is near to a release data of your kernel, that will
minimize the merge problems.
This one seems a good candidate:
http://git.fsl.cs.sunysb.edu/?p=wrapfs-latest.git;a=commit;h=e478bec0ba0a83a48a0f6982934b6de079e7e6b3
But why are you force to use such and old kernel? Seriously, 2.6.18 is
at least 5 years old.
If you are forced to use this kernel by a vendor, then ask your vendor
for support. Sorry, the community can't help you when using forked
kernels.
Hope it helps,
--
Javier Mart?nez Canillas
(+34) 682 39 81 69
Barcelona, Spain
next prev parent reply other threads:[~2012-04-05 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 4:32 wrapfs sources V.Ravikumar
2012-04-05 10:59 ` Javier Martinez Canillas [this message]
[not found] <CA+CftcGVR+Cq+C7iOf7HtTS-oDZ6x1SBkPLc-kVN0Mox-Fgtxw@mail.gmail.com>
[not found] ` <AA4DF347-38D4-4C66-A5AD-8ED0892BB242@cs.stonybrook.edu>
2012-04-06 8:24 ` V.Ravikumar
2012-04-10 5:50 ` Jim Cromie
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=CAAwP0s3gpZgbhPFUsiMV1P2ZEp+ekV7+AsKU8hOVy-ux7gavTQ@mail.gmail.com \
--to=martinez.javier@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).