From: dirk.behme@googlemail.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: arm linux porting effort
Date: Tue, 01 Sep 2009 11:10:37 +0200 [thread overview]
Message-ID: <4A9CE50D.40905@googlemail.com> (raw)
In-Reply-To: <ab40e9c0909010154i3cf6e51duf155fd3ca04ff92@mail.gmail.com>
Xu Yang wrote:
> hi guys,
>
> we already have linux kernel 2.6.29 running on our own arm1176
> platform. now I would like to upgrade the kernel to 2.6.30(or we can
> say to port 2.6.30 on our platform). I haven't done this before, so I
> don't know how much effort this means.
>
> anyone any ideas? or any hints?
From 2.6.29 to 2.6.30 you could try to let git do the work. Try to
git merge (or rebase?), resolve the conflicts, build, boot and check
if everything is still working. If you create an extra branch for
this, you will break nothing and will know the effort afterwards ;)
Best regards
Dirk
next prev parent reply other threads:[~2009-09-01 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 8:54 arm linux porting effort Xu Yang
2009-09-01 9:10 ` Dirk Behme [this message]
2009-09-01 9:29 ` Xu Yang
2009-09-01 9:22 ` Wan ZongShun
2009-09-01 9:30 ` Xu Yang
2009-09-01 9:44 ` Wan ZongShun
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=4A9CE50D.40905@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-arm-kernel@lists.infradead.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).