From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [patch] i2c: announce SMBus host controllers
Date: Fri, 4 Jan 2008 18:44:11 +0100 [thread overview]
Message-ID: <20080104184411.142fd0b2@hyperion.delvare> (raw)
In-Reply-To: <200801021635.04702.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Hi Bjorn,
On Wed, 2 Jan 2008 16:35:04 -0700, Bjorn Helgaas wrote:
> On Saturday 22 December 2007 09:10:44 am Jean Delvare wrote:
> > * I think that you should make sure that the device has been successfully
> > registered before you print the message, otherwise it might be
> > confusing. I only looked at i2c-pasemi and scx200_acb and for both
> > drivers you print the message at a point where a failure could still
> > happen. Please double-check for all drivers, adjust as needed and
> > resubmit.
>
> Take a look at i2c-ali1535.c. I put the new printk in ali1535_setup(),
> which does PCI initialization, even though a failure could happen later
> in i2c_add_adapter().
>
> I picked that because putting the new printk in ali1535_probe() would
> mean:
> - the printk would be far removed from the request_region(), so it's
> a little harder to be sure the "ali1535_smba + ALI1535_SMB_IOSIZE - 1"
> expression matches,
> - I wouldn't be able print the SMBREV value, and
> - I'd have to add a temporary to check the return from
> i2c_add_adapter() instead of just returning it directly,
>
> I'd still be glad to change them if you prefer. I just want to do
> them all the same (either all before or all after i2c_add_adapter()).
> Let me know your preference.
If moving the message makes the code mode complex, then I agree that
you shouldn't do that. After all, i2c_add_adapter() is very unlikely to
fail, and if it does, I certainly hope that it'll clearly show in the
kernel log so that no confusion is possible.
So just do what you think is best and I'll take that.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2008-01-04 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200712201801.28227.bjorn.helgaas@hp.com>
[not found] ` <200712201801.28227.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2007-12-22 16:10 ` [patch] i2c: announce SMBus host controllers Jean Delvare
[not found] ` <e3i3Vo4v.1198339842.7760000.khali-IO4AeUl/lkuWVfeAwA7xHQ@public.gmane.org>
2007-12-23 3:42 ` Bjorn Helgaas
2008-01-02 23:35 ` Bjorn Helgaas
[not found] ` <200801021635.04702.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2008-01-04 17:44 ` Jean Delvare [this message]
2008-01-04 19:03 ` Jean Delvare
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=20080104184411.142fd0b2@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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