From: martinez.javier@gmail.com (Javier Martinez Canillas)
To: kernelnewbies@lists.kernelnewbies.org
Subject: New kernel for Chipbox
Date: Fri, 8 Jun 2012 14:16:28 +0200 [thread overview]
Message-ID: <CAAwP0s2p_qfQpYkJMkF-y781oijpUk8T0i3ZP7g9p3sc1bNOwg@mail.gmail.com> (raw)
In-Reply-To: <03A5838C3F37465F97B39B15CA56C3AF@drejoasus>
On Thu, Jun 7, 2012 at 1:53 PM, Sertac TULLUK <sertac@merihvideo.com.tr> wrote:
> Dear Harishkumar;
>
> I already know how to find the changes, please see my 1st e-mail below.
>
> The problem is, those changes are more than thousands of lines of code, and
> hundreds of files are added or modified.
>
> I wonder, how can I apply those thousands of changes to new kernel source
> quickly and easily?
>
The bad news is that there isn't a quickly and easily way to do it.
The kernel doesn't have an stable API (read
Documentation/stable_api_nonsense.txt) and the ARM part of the kernel
is one of the most fast changing lately. So probably most of the
drivers and SoC enablement platform code won't work with newer
kernels.
So, this isn't a trivial task.
Best regards,
--
Javier Mart?nez Canillas
(+34) 682 39 81 69
Barcelona, Spain
next prev parent reply other threads:[~2012-06-08 12:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 9:06 New kernel for Chipbox Sertac TULLUK
2012-06-07 10:31 ` Harishkumar V
2012-06-07 11:06 ` Sertac TULLUK
2012-06-07 11:48 ` Harishkumar V
2012-06-07 11:52 ` Harishkumar V
2012-06-07 11:58 ` Sertac TULLUK
2012-06-07 12:17 ` Harishkumar V
2012-06-07 12:24 ` Sertac TULLUK
2012-06-07 12:29 ` Harishkumar V
2012-06-07 12:35 ` Sertac TULLUK
2012-06-07 12:37 ` Harishkumar V
2012-06-07 12:38 ` Harishkumar V
2012-06-07 11:53 ` Sertac TULLUK
2012-06-08 12:16 ` Javier Martinez Canillas [this message]
2012-06-09 19:06 ` Sertac TULLUK
2012-06-10 2:52 ` Harishkumar V
2012-06-10 17:42 ` Sertac TULLUK
2012-06-07 23:47 ` hooking above libata Com Developer
-- strict thread matches above, loose matches on Subject: below --
2012-06-07 13:07 New kernel for Chipbox Sertac TULLUK
2012-06-07 14:39 ` Harishkumar V
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=CAAwP0s2p_qfQpYkJMkF-y781oijpUk8T0i3ZP7g9p3sc1bNOwg@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).