Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Tomaso Paoletti <tpaoletti@caviumnetworks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 0/2] Initial support for OCTEON
Date: Tue, 19 Aug 2008 10:12:47 +0100	[thread overview]
Message-ID: <20080819091247.GB28692@linux-mips.org> (raw)
In-Reply-To: <48A9E6DA.8030208@caviumnetworks.com>

On Mon, Aug 18, 2008 at 02:17:14PM -0700, Tomaso Paoletti wrote:

> This is a first (trivial) set of patches to pave the way for support of  
> OCTEON processors in the kernel.
>
> The set adds:
> - Detection of OCTEON CPU variants in cpu_probe_cavium()
> - Processor ID (PrID) constants
> - Workaround (WAR) include file
>
> Please consider for inclusion.

So with the evil email monster having kept these mails without sharing them
with us...

I normally insist that there are users for new header files or functions
since otherwise the kernel janitors will remove them shortly ...

  Ralf

  reply	other threads:[~2008-08-19  9:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 21:17 [PATCH 0/2] Initial support for OCTEON Tomaso Paoletti
2008-08-19  9:12 ` Ralf Baechle [this message]
2008-08-20 20:29   ` Tomaso Paoletti
2008-08-20 20:20 ` [PATCH 1/2] OCTEON: Add processor-specific constants and detection of CPU variants Tomaso Paoletti
2008-08-20 22:33   ` Thomas Bogendoerfer
2008-08-21 16:32     ` Tomaso Paoletti
2008-08-20 20:20 ` [PATCH 2/2] OCTEON: Add workaround file Tomaso Paoletti
2008-08-21  6:58   ` Ralf Baechle
2008-08-22  1:45     ` Tomaso Paoletti
2008-08-22  1:21 ` [PATCH v2 1/2] OCTEON: Add processor-specific constants and detection of CPU variants Tomaso Paoletti
2008-08-22  1:43 ` [PATCH v2 2/2] OCTEON: Add workaround file Tomaso Paoletti

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=20080819091247.GB28692@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=tpaoletti@caviumnetworks.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