From: Greg KH <greg@kroah.com>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: linux-kernel@vger.kernel.org, "Saxena,
Sunil" <sunil.saxena@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Carbonari, Steven" <steven.carbonari@intel.com>
Subject: Re: RFC Proposal to enable MSI support in Linux kernel
Date: Wed, 14 May 2003 10:44:31 -0700 [thread overview]
Message-ID: <20030514174431.GA2750@kroah.com> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E50241361D9@orsmsx404.jf.intel.com>
Even though you are trying to withdraw this message (which is pointless
for something sent to a mailing list), I had a few small questions with
regards to PCI Hotplug devices:
> +/**
> + * msi_hp_free_vectors: reclaim all MSI previous assigned to this device
> + * argument: device pointer of type struct pci_dev
> + *
> + * description: used during hotplug removed, from which device is
> hot-removed;
Oops, your patch wrapped, please try another email client, or change the
configuration options of your current one.
> + * PCI subsystem reclaims associated MSI to unused state, which may be used
>
> + * later on.
> + **/
> +void remove_hotplug_vectors(void* dev_id)
> +{
> + struct msi_desc_t *entry;
> + struct pci_dev *dev = (struct pci_dev *)dev_id;
> + int type;
> + void *mask_entry_addr;
> + unsigned int flags;
Hm, wierd indenting style, can you just follow Documentation/CodingStyle
and use tabs?
Anyway, what code is supposed to use this function? A PCI Hotplug
controller driver? If so, do you have any patches to the current
drivers that show how it is used?
Also, why pass a void *? That's usually forbidden in the kernel, and
since you are instantly casting it to a struct pci_dev *, why not just
use that?
thanks,
greg k-h
next prev parent reply other threads:[~2003-05-14 17:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 15:22 RFC Proposal to enable MSI support in Linux kernel Nguyen, Tom L
2003-05-14 17:44 ` Greg KH [this message]
2003-05-14 18:58 ` Zwane Mwaikambo
2003-05-14 19:06 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 15:41 Nguyen, Tom L
2003-05-14 18:51 Nguyen, Tom L
2003-05-14 19:57 Nakajima, Jun
2003-05-14 19:54 ` Zwane Mwaikambo
2003-05-14 20:43 Nakajima, Jun
2003-05-19 21:22 Nguyen, Tom L
2003-05-20 10:36 ` Martin Schlemmer
2003-05-20 18:49 ` Zwane Mwaikambo
2003-05-28 22:22 ` Zwane Mwaikambo
2003-05-28 23:01 ` Jeff Garzik
2003-05-28 23:06 ` Zwane Mwaikambo
2003-05-28 23:45 ` Jeff Garzik
2003-05-28 23:50 ` Zwane Mwaikambo
2003-05-19 21:46 Nguyen, Tom L
2003-05-20 19:03 Nguyen, Tom L
2003-05-29 18:12 Nguyen, Tom L
2003-05-29 21:55 ` Zwane Mwaikambo
2003-05-30 2:14 Nakajima, Jun
2003-05-30 14:56 Nicolas Mailhot
2003-05-31 2:29 ` William Lee Irwin III
2003-05-31 7:13 ` Zwane Mwaikambo
2003-05-31 7:28 ` 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=20030514174431.GA2750@kroah.com \
--to=greg@kroah.com \
--cc=asit.k.mallick@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steven.carbonari@intel.com \
--cc=sunil.saxena@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.