mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: olof@austin.ibm.com (Olof Johansson)
Cc: paulus@samba.org, jgarzik@pobox.com, rene@exactcode.de,
	torvalds@osdl.org, linux-kernel@vger.kernel.org, greg@kroah.com,
	chrisw@osdl.org
Subject: Re: [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec
Date: Thu, 3 Mar 2005 17:59:51 -0800	[thread overview]
Message-ID: <20050303175951.41cda7a4.akpm@osdl.org> (raw)
In-Reply-To: <20050303225542.GB16886@austin.ibm.com>

olof@austin.ibm.com (Olof Johansson) wrote:
>
> Here's a patch that will work for both PPC and PPC64. The proper way to
>  fix this in mainline is to merge -mm's cpu_has_feature patch, but for
>  the stable 2.6.11-series, this much less intrusive (i.e. just the pure
>  bugfix, not the cleanup part).
> 
>  Signed-off-by: Olof Johansson <olof@austin.ibm.com>
> 
> 
>  Index: linux-2.5/drivers/md/raid6altivec.uc
>  ===================================================================
>  --- linux-2.5.orig/drivers/md/raid6altivec.uc	2005-03-03 16:46:47.000000000 -0600
>  +++ linux-2.5/drivers/md/raid6altivec.uc	2005-03-03 16:48:03.000000000 -0600
>  @@ -108,7 +108,11 @@ int raid6_have_altivec(void);
>   int raid6_have_altivec(void)
>   {
>   	/* This assumes either all CPUs have Altivec or none does */
>  +#ifdef CONFIG_PPC64
>  +	return cur_cpu_spec->cpu_features & CPU_FTR_ALTIVEC;
>  +#else
>   	return cur_cpu_spec[0]->cpu_features & CPU_FTR_ALTIVEC;
>  +#endif
>   }
>   #endif

This patch doesn't seem right - current 2.6.11 has:

        return cur_cpu_spec->cpu_features & CPU_FTR_ALTIVEC;

So anyway, I fixed it up as:

--- 25/drivers/md/raid6altivec.uc~ppc-raid6-altivec-build-fix	2005-03-03 17:56:21.000000000 -0800
+++ 25-akpm/drivers/md/raid6altivec.uc	2005-03-03 17:57:50.000000000 -0800
@@ -108,7 +108,11 @@ int raid6_have_altivec(void);
 int raid6_have_altivec(void)
 {
 	/* This assumes either all CPUs have Altivec or none does */
+#ifdef CONFIG_PPC64
 	return cur_cpu_spec->cpu_features & CPU_FTR_ALTIVEC;
+#else
+	return cur_cpu_spec[0]->cpu_features & CPU_FTR_ALTIVEC;
+#endif
 }
 #endif
 
_


I'll assume that the above is suitable as a temp thing and I'll fix up
ppc-ppc64-abstract-cpu_feature-checks.patch

  parent reply	other threads:[~2005-03-04  2:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 18:05 Rene Rebe
2005-03-03 18:26 ` Jeff Garzik
2005-03-03 18:48   ` Greg KH
2005-03-03 18:59     ` Rene Rebe
2005-03-03 19:18   ` Greg KH
2005-03-03 19:48     ` Jeff Garzik
2005-03-03 20:07       ` Chris Wright
2005-03-03 20:32         ` Greg KH
2005-03-03 20:57           ` Jeff Garzik
2005-03-04 12:10             ` Francois Romieu
2005-03-03 22:30   ` Paul Mackerras
2005-03-03 22:45     ` Greg KH
2005-03-03 23:05       ` Dave Jones
2005-03-03 22:55     ` Olof Johansson
2005-03-03 23:14       ` Greg KH
2005-03-04  1:59       ` Andrew Morton [this message]
2005-03-04  2:24         ` Olof Johansson
2005-03-04  5:54           ` Chris Wright
2005-03-04  6:06             ` Jeff Garzik
2005-03-04  6:17               ` Andrew Morton
2005-03-04  6:33                 ` Jeff Garzik
2005-03-04  6:06             ` Andrew Morton
2005-03-04  6:12               ` Jeff Garzik
2005-03-04  6:20                 ` Andrew Morton
2005-03-04  6:20                 ` Chris Wright
2005-03-04  6:23                   ` Andrew Morton
2005-03-04  6:47                     ` Chris Wright
2005-03-04  6:54                       ` Andrew Morton
2005-03-04  7:04                         ` Chris Wright
2005-03-04  7:05                       ` Jeff Garzik
2005-03-04  7:12                         ` Andrew Morton
2005-03-04  7:14                           ` Jeff Garzik
2005-03-04 16:27                     ` Greg KH
2005-03-04 18:38                       ` Linus Torvalds
2005-03-04 18:41                         ` Greg KH
2005-03-06 23:06                       ` Alan Cox
2005-03-07 18:03                         ` Alan Cox

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=20050303175951.41cda7a4.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@austin.ibm.com \
    --cc=paulus@samba.org \
    --cc=rene@exactcode.de \
    --cc=torvalds@osdl.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

Powered by JetHome