Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Fix a CPU definition for Cobalt
Date: Fri, 20 Jan 2006 15:10:05 +0000	[thread overview]
Message-ID: <20060120151005.GH4343@deprecation.cyrius.com> (raw)
In-Reply-To: <20060120150126.GB30415@linux-mips.org>

* Ralf Baechle <ralf@linux-mips.org> [2006-01-20 16:01]:
> > > pointer is eventually called as a function.  So I suggest this below.
> > > Can you test it?
> > Doesn't work.
> Indeed - for quite obvioius reasons even.  I hope I now covered all cases
> in the new patch below.

You attached the SERIO patch. ;-)
-- 
Martin Michlmayr
http://www.cyrius.com/

  reply	other threads:[~2006-01-20 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 19:24 Fix a CPU definition for Cobalt Martin Michlmayr
2006-01-19 21:04 ` Ralf Baechle
2006-01-19 21:45   ` Martin Michlmayr
2006-01-20 15:01     ` Ralf Baechle
2006-01-20 15:10       ` Martin Michlmayr [this message]
2006-01-20 15:19         ` Ralf Baechle
2006-01-20 16:00           ` Martin Michlmayr
2006-02-17 19:14     ` Martin Michlmayr

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=20060120151005.GH4343@deprecation.cyrius.com \
    --to=tbm@cyrius.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