Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-mips@linux-mips.org, Michael Buesch <mb@bu3sch.de>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: pending mips build fixes
Date: Thu, 12 Jun 2008 14:58:35 +0100	[thread overview]
Message-ID: <20080612135835.GB20015@linux-mips.org> (raw)
In-Reply-To: <20080612134539.GA20487@cs181133002.pp.htv.fi>

On Thu, Jun 12, 2008 at 04:45:40PM +0300, Adrian Bunk wrote:
> From: Adrian Bunk <bunk@kernel.org>
> Date: Thu, 12 Jun 2008 16:45:40 +0300
> To: ralf@linux-mips.org
> Cc: linux-mips@linux-mips.org, Michael Buesch <mb@bu3sch.de>,
> 	Aurelien Jarno <aurelien@aurel32.net>,
> 	Atsushi Nemoto <anemo@mba.ocn.ne.jp>
> Subject: pending mips build fixes
> Content-Type: text/plain; charset=utf-8
> 
> Hi Ralf,
> 
> I hope I'm not too annoying on this, but I like it when as many 
> defconfigs as possible compile.
> 
> Please review and push the following patches for 2.6.26:
> 
>   BCM47xx: Add platform specific PCI code
>   http://marc.info/?l=linux-kernel&amp;m=120876451216558&amp;w=2
> 
>   MIPS: Fix CONF_CM_DEFAULT build error
>   http://lkml.org/lkml/2008/6/1/125

That won't fly.  CONF_CM_DEFAULT is being dereferenced before
_page_cachable_default has been initialized.

Can't comment at the BCM47xx patch yet.

  Ralf

  reply	other threads:[~2008-06-12 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 13:45 pending mips build fixes Adrian Bunk
2008-06-12 13:58 ` Ralf Baechle [this message]
2008-06-12 14:31   ` Michael Buesch
2008-06-23  7:39     ` Aurelien Jarno
2008-06-12 15:03   ` Atsushi Nemoto
2008-06-12 16:23     ` Ralf Baechle
2008-06-12 19:49       ` danieljlaird
2008-06-12 19:49         ` danieljlaird

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=20080612135835.GB20015@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=aurelien@aurel32.net \
    --cc=bunk@kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mb@bu3sch.de \
    /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