From: Ralf Baechle <ralf@linux-mips.org>
To: Franck <vagabon.xyz@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] minor fix in asm-mips/module.h
Date: Fri, 30 Sep 2005 17:09:52 +0100 [thread overview]
Message-ID: <20050930160952.GB13616@linux-mips.org> (raw)
In-Reply-To: <cda58cb80509300844v5181d6fey@mail.gmail.com>
On Fri, Sep 30, 2005 at 05:44: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.
Yes, some people do strange things with Linux :-)
Ralf
prev parent reply other threads:[~2005-09-30 16:10 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
2005-09-30 16:09 ` Ralf Baechle [this message]
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=20050930160952.GB13616@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=vagabon.xyz@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