From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: "Jeff Garzik" <jgarzik@pobox.com>,
"long" <tlnguyen@snoqualmie.dp.intel.com>
Cc: <linux-kernel@vger.kernel.org>,
"Nguyen, Tom L" <tom.l.nguyen@intel.com>, <greg@kroah.com>
Subject: RE: Updated MSI Patches
Date: Thu, 7 Aug 2003 16:07:53 -0700 [thread overview]
Message-ID: <7F740D512C7C1046AB53446D3720017304AE7D@scsmsx402.sc.intel.com> (raw)
> Seems like a lot of this file could go into a new file,
> drivers/pci/msi.c. We'll want to share as much code as possible
across
> all Linux architectures.
Agree.
At the same time, Long, you need to provide more info so that more
people can play with MSI.
Jun
> -----Original Message-----
> From: Jeff Garzik [mailto:jgarzik@pobox.com]
> Sent: Thursday, August 07, 2003 3:45 PM
> To: long
> Cc: linux-kernel@vger.kernel.org; Nakajima, Jun; Nguyen, Tom L;
> greg@kroah.com
> Subject: Re: Updated MSI Patches
>
> long wrote:
>
>
> > diff -X excludes -urN linux-2.6.0-test2-create-
> vectorbase/arch/i386/kernel/pci_msi.c linux-2.6.0-test2-create-
> msi/arch/i386/kernel/pci_msi.c
> > --- linux-2.6.0-test2-create-vectorbase/arch/i386/kernel/pci_msi.c
> 1969-12-31 19:00:00.000000000 -0500
> > +++ linux-2.6.0-test2-create-msi/arch/i386/kernel/pci_msi.c 2003-08-
> 06 09:47:02.000000000 -0400
>
> Seems like a lot of this file could go into a new file,
> drivers/pci/msi.c. We'll want to share as much code as possible
across
> all Linux architectures.
>
> Jeff
>
next reply other threads:[~2003-08-07 23:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 23:07 Nakajima, Jun [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 22:15 Updated MSI Patches long
2003-10-01 18:26 Nguyen, Tom L
2003-10-01 15:37 long
2003-10-01 17:09 ` Jeff Garzik
2003-08-22 18:25 long
2003-08-19 15:42 Nguyen, Tom L
2003-08-14 23:46 Nguyen, Tom L
2003-08-13 15:19 Nguyen, Tom L
2003-08-13 4:14 Nakajima, Jun
2003-08-13 1:34 Nakajima, Jun
2003-08-13 1:37 ` Zwane Mwaikambo
2003-08-12 23:59 Nakajima, Jun
2003-08-13 0:48 ` Zwane Mwaikambo
2003-08-12 18:36 Nakajima, Jun
2003-08-12 18:48 ` Jeff Garzik
2003-08-12 19:14 ` Zwane Mwaikambo
2003-08-12 19:44 ` Jeff Garzik
2003-08-12 17:32 Nguyen, Tom L
2003-08-12 18:14 ` Zwane Mwaikambo
2003-08-12 17:04 Nguyen, Tom L
2003-08-12 18:11 ` Zwane Mwaikambo
2003-08-12 15:22 long
2003-08-11 20:51 long
2003-08-11 21:16 ` Greg KH
2003-08-12 1:41 ` Zwane Mwaikambo
2003-08-12 5:53 ` Greg KH
2003-08-08 19:33 long
2003-08-08 20:15 ` Greg KH
2003-08-08 14:41 Nguyen, Tom L
2003-08-07 21:25 long
2003-08-07 22:14 ` Greg KH
2003-08-07 22:44 ` Jeff Garzik
2003-08-07 23:03 ` Matt Porter
2003-08-08 2:36 ` Zwane Mwaikambo
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=7F740D512C7C1046AB53446D3720017304AE7D@scsmsx402.sc.intel.com \
--to=jun.nakajima@intel.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).