[lkml]   [2005]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 16/42]: PCI: PCI Error reporting callbacks
On Thu, Nov 03, 2005 at 06:50:35PM -0600, Linas Vepstas wrote:
> +/* ---------------------------------------------------------------- */
> +/** PCI error recovery infrastructure. If a PCI device driver provides
> + * a set fof callbacks in struct pci_error_handlers, then that device driver
> + * will be notified of PCI bus errors, and will be driven to recovery
> + * when an error occurs.
> + */
> +
> +enum pcierr_result {
> + PCIERR_RESULT_NONE=0, /* no result/none/not supported in device driver */
> + PCIERR_RESULT_CAN_RECOVER=1, /* Device driver can recover without slot reset */
> + PCIERR_RESULT_NEED_RESET, /* Device driver wants slot to be reset. */
> + PCIERR_RESULT_DISCONNECT, /* Device has completely failed, is unrecoverable */
> + PCIERR_RESULT_RECOVERED, /* Device driver is fully recovered and operational */
> +};

No, do not create new types of error or return codes. Use the standard
-EFOO values. You can document what they should each return, and mean,
but do not create new codes.

Also, you create an enum, but yet do not use it in your function
callback definition, which means you really didn't want to create it in
the first place...

I'll add 15 and 16 to my tree for now, so they will show up in -mm, but
I want to see updated versions before sending them off to Linus.


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-11-05 07:14    [W:0.223 / U:0.360 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site