netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Brown <mbrown@fensystems.co.uk>
To: Jean Delvare <khali@linux-fr.org>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
	Jeff Garzik <jgarzik@redhat.com>,
	netdev@vger.kernel.org, Linux I2C <i2c@lm-sensors.org>,
	linux-net-drivers@solarflare.com
Subject: Re: SFC driver implements its own I2C support
Date: Thu, 15 May 2008 15:52:42 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0805151551330.13626@dolphin.home> (raw)
In-Reply-To: <20080515143954.15bc4170@hyperion.delvare>

On Thu, 15 May 2008, Jean Delvare wrote:
> > I think there may also have been issues with the fact that the i2c 
> > system allows for failures on the shutdown path (e.g. 
> > i2c_detach_client() can return a failure), which becomes awkward to 
> > handle when you are in the middle of a shutdown path that is not 
> > allowed to fail (e.g. a pci_driver->remove method).
> 
> This part of the code has been reworked completely. That being said, I 
> see that the i2c_driver remove method returns an int not void, so it can 
> still fail. There doesn't seem to be a common behavior in this respect 
> amongst subsystems, some allow the remove method to fail and others 
> don't. If you think that the i2c subsystem should not let remove methods 
> fail, we can discuss this. But most likely, the error code is purely 
> informative so it doesn't really matter if we return it or void.

It does matter if the i2c remove failure indicates that data structures 
are still left linked in to various lists etc.

Michael

  parent reply	other threads:[~2008-05-15 14:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  8:33 SFC driver implements its own I2C support Jean Delvare
2008-05-14 21:58 ` Ben Hutchings
2008-05-15  9:24   ` Jean Delvare
2008-05-15 12:04     ` Michael Brown
2008-05-15 12:39       ` Jean Delvare
2008-05-15 12:58         ` [i2c] " Wolfram Sang
2008-05-15 14:52         ` Michael Brown [this message]
2008-05-15 12:03   ` Riku Voipio

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=Pine.LNX.4.62.0805151551330.13626@dolphin.home \
    --to=mbrown@fensystems.co.uk \
    --cc=bhutchings@solarflare.com \
    --cc=i2c@lm-sensors.org \
    --cc=jgarzik@redhat.com \
    --cc=khali@linux-fr.org \
    --cc=linux-net-drivers@solarflare.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).