mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, jeff@garzik.org
Subject: Re: + drivers-ide-fix-error-return-bugs-interface.patch added to -mm tree
Date: Sun, 15 Oct 2006 15:46:46 +0100	[thread overview]
Message-ID: <1160923606.5732.61.camel@localhost.localdomain> (raw)
In-Reply-To: <200610102047.k9AKl53O022518@shell0.pdx.osdl.net>

Ar Maw, 2006-10-10 am 13:47 -0700, ysgrifennodd akpm@osdl.org:
> This fixes the following error handling problems:
> 
> * The init_chipset API function is defined to return 'unsigned int', but
> 	- the caller code tests the return value for '< 0'
> 	- drivers sometimes return a negative value

Dropped for good. The core code doesn't support failing in init_chipset.
Instead I've adjusted via82cxxx to do the check earlier in init_one().
Also avoids an API change and all the noise.

> * cs5530: handle pci_set_mwi() failure with a printk()... shouldn't kill driver

NAK. Fix is to remove bogus must_check from pci_set_mwi (and some of the
other functions)

> * sc1200: handle pci_enable_device() failure during resume

NAK: if the pci_enable_device fails here the best we can do is attempt
to get it back and hope the pci_enable_device failure is bogus. This is
a can't happen case anyway so its a waste of memory. If you insist on
checking pci_enable_device returns everywhere then please move the
printk into the pci_enable_device function so that we don't bloat the
kernel with a load of pointless identically messages for an event that
never happen, one per driver.

Alan


           reply	other threads:[~2006-10-15 14:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200610102047.k9AKl53O022518@shell0.pdx.osdl.net>]

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=1160923606.5732.61.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®