On Tue, 2012-11-27 at 20:32 +0100, Manuel Lauss wrote: > On Tue, Nov 27, 2012 at 7:15 PM, Shuah Khan <[email protected]> wrote: > > On Tue, 2012-11-27 at 18:15 +0100, Ralf Baechle wrote: > >> On Mon, Nov 26, 2012 at 07:19:45PM -0700, Shuah Khan wrote: > >> > >> > Should this patch go into stable? My guess is that compiles will > >> > fail the same way 3.4.x and 3.6.x as well with CC 4.4 and newer. > >> > > >> > http://marc.info/?l=git-commits-head&m=135389577115917&w=2 > >> > > >> > It is not marked for stable and maybe that is what is intended. Just > >> > wanting to confirm. > >> > >> It should go to -stable as well. > >> > > > > Hmm. I can't reproduce the compile error. I am using cross-compile on > > x86_64 and tried with mipsel-linux-gnu-gcc-4.7 and > > mips-linux-gnu-gcc-4.7 both. I tried it on linux-next Nov 20th as well > > as the latest linux-3.4.y > > As far as I can see, MPI first appeared in 3.6, although I can't find a switch > to enable it, at least on my mips builds. With 3.7-rc a selectable X.509 > parser > appeared in the crypto menu which selects MPI. > > > > What am I missing? Is gcc4.7 older and doesn't show the problem? I think > > I am missing something very obvious. > > With 3.7-rc5 and a more or less vanilla gcc-4.7.2:
Looks like the issue with my compile failure is CONFIG_MPILIB not being enabled. I don't seem to be able to find the magic combination config options to enable CONFIG_MPILIB to test this patch on stable. I tried forcing db1235_defconfig to be the defconfig for mips, still no luck. If this patch is needed in stable 3.6 release, do you mind testing it on stable and sending it to stable including the upstream commit id information? Thanks, -- Shuah -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
