From: Roland Dreier <rolandd@cisco.com>
To: Andi Kleen <ak@suse.de>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
discuss@x86-64.org
Subject: Re: [PATCH] x86_64: Work around Re: 2.6.14-git1 (and -git2) build failure on AMD64
Date: Sun, 30 Oct 2005 08:17:39 -0800 [thread overview]
Message-ID: <52br17nfmk.fsf@cisco.com> (raw)
In-Reply-To: <200510301649.42064.ak@suse.de> (Andi Kleen's message of "Sun, 30 Oct 2005 16:49:41 +0100")
Andi> Linus, can you please apply it?
No, please don't apply this. The correct fix is to mark
toshiba_ohci1394_dmi_table[] as __devinitdata in that file, as in the
patch I posted here:
http://lkml.org/lkml/2005/10/29/12
- R.
next prev parent reply other threads:[~2005-10-30 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 14:03 2.6.14-git1 (and -git2) build failure on AMD64 Martin J. Bligh
2005-10-30 14:17 ` Roland Dreier
2005-10-30 15:28 ` Andi Kleen
2005-10-30 15:50 ` Martin J. Bligh
2005-10-30 16:15 ` Roland Dreier
2005-10-30 15:49 ` [PATCH] x86_64: Work around " Andi Kleen
2005-10-30 16:17 ` Roland Dreier [this message]
2005-10-30 16:23 ` Andi Kleen
2005-10-30 16:32 ` Roland Dreier
2005-11-02 5:16 ` Martin J. Bligh
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=52br17nfmk.fsf@cisco.com \
--to=rolandd@cisco.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.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