Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262816AbVAQO7O (ORCPT ); Mon, 17 Jan 2005 09:59:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262817AbVAQO7O (ORCPT ); Mon, 17 Jan 2005 09:59:14 -0500 Received: from de01egw02.freescale.net ([192.88.165.103]:46790 "EHLO de01egw02.freescale.net") by vger.kernel.org with ESMTP id S262816AbVAQO7M (ORCPT ); Mon, 17 Jan 2005 09:59:12 -0500 In-Reply-To: <1105956993.26551.327.camel@hades.cambridge.redhat.com> References: <1105956993.26551.327.camel@hades.cambridge.redhat.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <38A2A735-6898-11D9-AF22-000393DBC2E8@freescale.com> Content-Transfer-Encoding: 7bit Cc: , "Olaf Hering" , , , From: Kumar Gala Subject: Re: [PATCH] raid6: altivec support Date: Mon, 17 Jan 2005 08:58:17 -0600 To: "David Woodhouse" X-Mailer: Apple Mail (2.619) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 585 Lines: 16 [snip] > This makes it compile on PPC, but highlights the difference between > 'cur_cpu_spec' on ppc32 and ppc64. Why is 'cur_cpu_spec' an array on > ppc32? Isn't 'cur' supposed to imply 'current'? I can only guess to handle an SMP case with two different revs of the same processor that might have slightly different errata. - kumar - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/