From: Greg KH <greg@kroah.com>
To: akpm@osdl.org, tlnguyen@snoqualmie.dp.intel.com, tom.l.nguyen@intel.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ia32 Message Signalled Interrupt support
Date: Tue, 30 Dec 2003 10:38:29 -0800 [thread overview]
Message-ID: <20031230183829.GA2564@kroah.com> (raw)
In-Reply-To: <200312300711.hBU7BPKX023057@hera.kernel.org>
On Tue, Dec 30, 2003 at 05:42:23AM +0000, Linux Kernel Mailing List wrote:
> ChangeSet 1.1496.22.9, 2003/12/29 21:42:23-08:00, akpm@osdl.org
>
> [PATCH] ia32 Message Signalled Interrupt support
>
> From: long <tlnguyen@snoqualmie.dp.intel.com>
>
>
> Add support for Message Signalled Interrupt delivery on ia32.
>
> With a fix from Zwane Mwaikambo <zwane@arm.linux.org.uk>
<snip>
> diff -Nru a/drivers/pci/msi.c b/drivers/pci/msi.c
> --- /dev/null Wed Dec 31 16:00:00 1969
> +++ b/drivers/pci/msi.c Mon Dec 29 23:11:29 2003
> @@ -0,0 +1,1068 @@
> +/*
> + * linux/drivers/pci/msi.c
> + */
I'm guessing this file was written by Intel? If so, can we please get a
copyright statement for it? I'm getting tired of having to talk to
lawyers as it is...
thanks,
greg k-h
parent reply other threads:[~2003-12-30 18:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200312300711.hBU7BPKX023057@hera.kernel.org>]
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=20031230183829.GA2564@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--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