mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tim Hockin" <thockin@google.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: "Roland Dreier" <rdreier@cisco.com>,
	"Randy Dunlap" <randy.dunlap@oracle.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Kconfig variable "COBALT" is not defined anywhere
Date: Sun, 3 Jun 2007 14:38:00 -0700	[thread overview]
Message-ID: <cc96a5040706031438o667e4df0wb18bdd071f48e246@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706031714070.19004@localhost.localdomain>

I think the nvram is the only place left that uses CONFIG_COBALT

On 6/3/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> On Sun, 3 Jun 2007, Tim Hockin wrote:
>
> > There were other patches which added more COBALT support, but they
> > were dropped or lost or whatever.
> >
> > I would not balk at having that code yanked.  I never got around to
> > doing proper Cobalt support for modern kernels. :(
> >
> > On 6/3/07, Roland Dreier <rdreier@cisco.com> wrote:
> > >  > > >   there is no Kconfig file which defines the selectable option
> > >  > > > "COBALT", which means that this snippet from drivers/char/nvram.c:
> > >  > > >
> > >  > > > #  if defined(CONFIG_COBALT)
> > >  > > > #    include <linux/cobalt-nvram.h>
> > >  > > > #    define MACH COBALT
> > >  > > > #  else
> > >  > > > #    define MACH PC
> > >  > > > #  endif
> > >  > > > never evaluates to true, therefore making <linux/cobalt-nvram.h>
> > >  > > > fairly useless, at least under the circumstances.
> > >
> > >  > > Maybe it should be MIPS_COBALT ?
> > >
> > >  > that's the first thing that occurred to me, but that header file is
> > >  > copyright sun microsystems and says nothing about MIPS, so that didn't
> > >  > really settle the issue.  that's why i'd rather someone else resolve
> > >  > this one way or the other.
> > >
> > > Actually, looking through the old kernel history, it looks like this
> > > was added by Tim Hockin's (CCed) patch "Add Cobalt Networks support to
> > > nvram driver".  Which added this to drivers/cobalt:
> > >
> > > +bool 'Support for Cobalt Networks x86 servers' CONFIG_COBALT
> > >
> > > I guess Tim can clear up what's intended...
>
> ok, that sounds like it might be a bigger issue than just a dead
> CONFIG variable.  if that's all it is, i can submit a patch.  if it's
> more than that, i'll leave it to someone higher up the food chain to
> figure out what cobalt-related stuff should be yanked.
>
> rday
> --
> ========================================================================
> Robert P. J. Day
> Linux Consulting, Training and Annoying Kernel Pedantry
> Waterloo, Ontario, CANADA
>
> http://fsdev.net/wiki/index.php?title=Main_Page
> ========================================================================
>

  reply	other threads:[~2007-06-03 21:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 17:17 Robert P. J. Day
2007-06-03 20:23 ` Randy Dunlap
2007-06-03 20:31   ` Robert P. J. Day
2007-06-03 20:45     ` Roland Dreier
2007-06-03 21:08       ` Tim Hockin
2007-06-03 21:15         ` Robert P. J. Day
2007-06-03 21:38           ` Tim Hockin [this message]
2007-06-03 21:50             ` Robert P. J. Day
2007-06-04  3:15               ` Tim Hockin

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=cc96a5040706031438o667e4df0wb18bdd071f48e246@mail.gmail.com \
    --to=thockin@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rdreier@cisco.com \
    --cc=rpjday@mindspring.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

all inboxes | Powered by JetHome®