mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: akpm@osdl.org, tlnguyen@snoqualmie.dp.intel.com,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	ak@suse.de
Subject: Re: [PATCH]2.6.7-rc1 Fix and Reenable MSI Support on x86_64
Date: Mon, 7 Jun 2004 09:33:24 -0700	[thread overview]
Message-ID: <20040607093324.734455a6.rddunlap@osdl.org> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E502405570621@orsmsx404.amr.corp.intel.com>

On Mon, 7 Jun 2004 09:28:31 -0700 Nguyen, Tom L wrote:

| On Friday, June 04, 2004 Andrew Morton wrote: 
| 
| >>
| >> 
| >>  MSI support for x86_64 is currently disabled in the kernel 2.6.x.
| >>  Below is the patch, which provides a fix and reenable it.
| >
| >Could you please fix this up?
| >
| >arch/x86_64/kernel/i8259.c:118: warning: excess elements in array
| initializer
| >arch/x86_64/kernel/i8259.c:118: warning: (near initialization for
| `interrupt')
| >
| >.config is at http://www.zip.com.au/~akpm/linux/patches/stuff/config
| 
| Yes, I am looking into it right now. Please let me know which kernel you
| detected these warnings; so, I can repeat these warnings.

This is too simple, I guess, but I'd like to see .config contain
kernel version info....
updated by any "make *config", of course.

--
~Randy

  reply	other threads:[~2004-06-07 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 16:28 Nguyen, Tom L
2004-06-07 16:33 ` Randy.Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-04  1:20 long
2004-06-05  6:11 ` Andrew Morton

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=20040607093324.734455a6.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tlnguyen@snoqualmie.dp.intel.com \
    --cc=tom.l.nguyen@intel.com \
    /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

all inboxes | Powered by JetHome®