From: Peter Oruba <peter.oruba@amd.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 05/11] [PATCH 05/11] x86: Moved microcode.c to microcode_intel.c.
Date: Fri, 12 Sep 2008 13:54:20 +0200 [thread overview]
Message-ID: <48CA586C.2010104@amd.com> (raw)
In-Reply-To: <20080907120823.59f8fa47@infradead.org>
Arjan,
could you please provide some more information about that issue?
Thanks,
Peter
Arjan van de Ven schrieb:
> On Mon, 28 Jul 2008 18:44:16 +0200
> Peter Oruba <peter.oruba@amd.com> wrote:
>
>> Signed-off-by: Peter Oruba <peter.oruba@amd.com>
>> ---
>> arch/x86/kernel/Makefile | 2 +-
>> arch/x86/kernel/microcode.c | 855
>
> \
>
>
> unfortunately this patch breaks userland for me; the Fedora initscripts
> suddenly fail (with a [FAILED] that will alarm users) because of this
> rename....
> (well it also fails to update the microcode, and if you load the new
> module name by hand first it still fails in many ways ;-( )
>
> That is a regression in -tip unfortunately....
>
>
next prev parent reply other threads:[~2008-09-12 11:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 16:44 [patch 00/11] x86: AMD microcode patch loading support v2 Peter Oruba
2008-07-28 16:44 ` [patch 02/11] [PATCH 02/11] x86: Moved Intel microcode patch loader declarations to seperate header file Peter Oruba
2008-07-28 16:44 ` [patch 03/11] [PATCH 03/11] x86: Typedef removal Peter Oruba
2008-07-28 16:44 ` [patch 04/11] [PATCH 04/11] x86: Moved per CPU microcode structure declaration to header file Peter Oruba
2008-07-28 16:44 ` [patch 05/11] [PATCH 05/11] x86: Moved microcode.c to microcode_intel.c Peter Oruba
2008-09-07 19:08 ` Arjan van de Ven
2008-09-12 11:54 ` Peter Oruba [this message]
2008-09-12 13:35 ` Arjan van de Ven
2008-09-12 13:53 ` Giacomo A. Catenazzi
2008-09-19 11:59 ` Peter Oruba
2008-09-19 12:37 ` Dmitry Adamushko
2008-09-19 12:58 ` Giacomo A. Catenazzi
2008-09-19 13:03 ` Peter Oruba
2008-09-19 13:52 ` Giacomo A. Catenazzi
2008-09-20 6:11 ` Ingo Molnar
2008-09-19 14:06 ` Giacomo A. Catenazzi
2008-09-19 14:29 ` Arjan van de Ven
2008-09-20 6:07 ` Ingo Molnar
2008-09-19 13:07 ` Arjan van de Ven
2008-07-28 16:44 ` [patch 06/11] [PATCH 06/11] x86: Code split to two parts Peter Oruba
2008-07-28 16:44 ` [patch 07/11] [PATCH 07/11] x86: Structure declaration renaming Peter Oruba
2008-07-28 16:44 ` [patch 08/11] [PATCH 08/11] x86: Add AMD specific declarations Peter Oruba
2008-07-28 16:44 ` [patch 09/11] [PATCH 09/11] x86: First step of refactoring, introducing microcode_ops Peter Oruba
2008-07-28 16:44 ` [patch 10/11] [PATCH 10/11] x86: Major refactoring Peter Oruba
2008-07-28 19:36 ` Max Krasnyansky
2008-07-28 19:50 ` Tigran Aivazian
2008-07-28 16:44 ` [patch 11/11] [PATCH 11/11] x86: AMD microcode patch loading support Peter Oruba
2008-07-28 18:01 ` [patch 00/11] x86: AMD microcode patch loading support v2 Ingo Molnar
2008-07-29 8:10 ` [PATCH] x86, microcode support: fix build error Ingo Molnar
2008-07-29 8:10 ` [patch 00/11] x86: AMD microcode patch loading support v2 Ingo Molnar
2008-07-29 8:10 ` Ingo Molnar
2008-07-29 8:12 ` Ingo Molnar
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=48CA586C.2010104@amd.com \
--to=peter.oruba@amd.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tigran@aivazian.fsnet.co.uk \
/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