All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomaso Paoletti <tpaoletti@caviumnetworks.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] OCTEON: Add processor-specific constants and detection of CPU variants
Date: Thu, 21 Aug 2008 09:32:59 -0700	[thread overview]
Message-ID: <48AD98BB.9090908@caviumnetworks.com> (raw)
In-Reply-To: <20080820223358.GA9770@alpha.franken.de>

Hi Thomas

Thomas Bogendoerfer wrote:
> On Wed, Aug 20, 2008 at 01:20:05PM -0700, Tomaso Paoletti wrote:
>> --- a/include/asm-mips/bootinfo.h
>> +++ b/include/asm-mips/bootinfo.h
>> @@ -57,6 +57,11 @@
>>  #define	MACH_MIKROTIK_RB532	0	/* Mikrotik RouterBoard 532 	*/
>>  #define MACH_MIKROTIK_RB532A	1	/* Mikrotik RouterBoard 532A 	*/
>>  
>> +/*
>> + * Valid machtype for group CAVIUM
>> + */
>> +#define  MACH_CAVIUM_OCTEON	1	/* Cavium Octeon */
>> +
> 
> no new machtypes please.

Thanks, I've corrected that.
I'm waiting to see if there's more feedback, and will resend the patch 
by this afternoon (PST).

   Tomaso

  reply	other threads:[~2008-08-21 16:34 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
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 [this message]
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=48AD98BB.9090908@caviumnetworks.com \
    --to=tpaoletti@caviumnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=tsbogend@alpha.franken.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.