Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Franck <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] minor fix in asm-mips/module.h
Date: Fri, 30 Sep 2005 17:44:01 +0200	[thread overview]
Message-ID: <cda58cb80509300844v5181d6fey@mail.gmail.com> (raw)
In-Reply-To: <20050930130928.GA3083@linux-mips.org>

2005/9/30, Ralf Baechle <ralf@linux-mips.org>:
> On Fri, Sep 30, 2005 at 02:36:01PM +0200, Franck wrote:
>
> > 2005/9/30, Ralf Baechle <ralf@linux-mips.org>:
> > > There are no CONFIG_CPU_4KSC and CONFIG_CPU_4KSD configuration options.
> > > Did you really create this patch against the linux module of the CVS
> > > repository or was it a different tree?
> > >
> >
> > The patch was created against linux-mips CVS repository. I added 4KSC
> > and 4KSD support in this tree. I thougth seeing reference of 4KSC
> > somewhere. Anyway, if you don't want to include them in your tree
> > that's ok.
>
> It's just that references to CONFIG_* symbols that are being defined
> nowhere don't make sense.  If however you want to contribute improved
> support for these processors, by all means I'm certainly going to appreciate
> a patch!
>

I'm surprised you're interested in added support for 4KSC and 4KSD
cpu...Anyway I could send a trivial patch to you if so.

Thanks
--
               Franck

  reply	other threads:[~2005-09-30 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26  7:06 [PATCH] minor fix in asm-mips/module.h Franck
2005-09-26 11:55 ` Ralf Baechle
2005-09-26 12:05   ` Franck
2005-09-29 23:45     ` Ralf Baechle
2005-09-30 12:36       ` Franck
2005-09-30 13:09         ` Ralf Baechle
2005-09-30 15:44           ` Franck [this message]
2005-09-30 16:09             ` 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=cda58cb80509300844v5181d6fey@mail.gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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