From: Ralf Baechle <ralf@linux-mips.org>
To: "P. Christeas" <p_christ@hol.gr>
Cc: linux-mips@linux-mips.org, zhuzhenhua <zzh.hust@gmail.com>
Subject: Re: why the early_initcall(au1x00_setup) do not work?
Date: Mon, 9 Jan 2006 15:24:29 +0000 [thread overview]
Message-ID: <20060109152429.GE4286@linux-mips.org> (raw)
In-Reply-To: <200601091720.03822.p_christ@hol.gr>
On Mon, Jan 09, 2006 at 05:20:01PM +0200, P. Christeas wrote:
> > You've downloaded a kernel.org kernel it would seem - doesn't fly for MIPS.
> > Instead get a kernel from linux-mips.org.
> >
> > The early_initcall() construct has been removed.
> >
> > Ralf
>
> What's the difference between the trees?
All the MIPS work is happening in the linux-mips.org tree.
> Aren't the MIPS patches supposed to be merged to Linus' tree?
In 2.6.15 things were alomst fully merged but several megabytes of
patches are between the linux-mips.org and kernel.org versions of 2.6.14.
Ralf
next prev parent reply other threads:[~2006-01-09 15:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 5:59 why the early_initcall(au1x00_setup) do not work? zhuzhenhua
2006-01-09 14:56 ` Ralf Baechle
2006-01-09 15:20 ` P. Christeas
2006-01-09 15:24 ` Ralf Baechle [this message]
2006-01-10 1:02 ` zhuzhenhua
2006-01-10 14:19 ` Ralf Baechle
2006-01-10 15:40 ` Ivan Korzakow
2006-01-10 15:57 ` P. Christeas
2006-01-10 16:38 ` Ivan Korzakow
2006-01-10 16:57 ` P. Christeas
2006-01-10 17:15 ` Ivan Korzakow
2006-01-10 23:20 ` Ralf Baechle
2006-01-11 15:17 ` Ivan Korzakow
2006-01-10 21:53 ` Ralf Baechle
2006-01-11 11:10 ` Ivan Korzakow
2006-01-11 11:20 ` Ralf Baechle
2006-01-11 15:07 ` Ivan Korzakow
2006-01-11 19:07 ` Ralf Baechle
2006-01-11 15:14 ` Ivan Korzakow
2006-01-10 17:38 ` Jordan Crouse
2006-01-11 2:04 ` zhuzhenhua
2006-01-11 12:16 ` Ralf Baechle
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=20060109152429.GE4286@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=p_christ@hol.gr \
--cc=zzh.hust@gmail.com \
/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