linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: risingsunxy@googlemail.com (Xu Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: arm linux porting effort
Date: Tue, 1 Sep 2009 10:54:03 +0200	[thread overview]
Message-ID: <ab40e9c0909010154i3cf6e51duf155fd3ca04ff92@mail.gmail.com> (raw)

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?

thanks,

best regards,


Yang

             reply	other threads:[~2009-09-01  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01  8:54 Xu Yang [this message]
2009-09-01  9:10 ` arm linux porting effort Dirk Behme
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=ab40e9c0909010154i3cf6e51duf155fd3ca04ff92@mail.gmail.com \
    --to=risingsunxy@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).