Re: Kconfig variable "COBALT" is not defined anywhere

["Tim Hockin" <thockin@hockin.org>]

That sounds correct.

On 6/3/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> On Sun, 3 Jun 2007, Tim Hockin wrote:
>
> > I think the nvram is the only place left that uses CONFIG_COBALT
>
> sure, but once you remove this snippet near the top of
> drivers/char/nvram.c:
>
> ...
> #  if defined(CONFIG_COBALT)
> #    include <linux/cobalt-nvram.h>
> #    define MACH COBALT
> #  else
> #    define MACH PC
> #  endif
> ...
>
> then everything else COBALT-related in that file should be tossed as
> well, which would include stuff conditional on:
>
>   #if MACH == COBALT
>
> and so on.  just making sure that what you're saying is that *all*
> COBALT-related content in that file can be thrown out.  i'll submit a
> patch shortly and you can pass judgment.
>
> rday
> --
> ========================================================================
> Robert P. J. Day
> Linux Consulting, Training and Annoying Kernel Pedantry
> Waterloo, Ontario, CANADA
>
> http://fsdev.net/wiki/index.php?title=Main_Page
> ========================================================================
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>