public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: djwong@us.ibm.com
Cc: Crane Cai <crane.cai@amd.com>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	lenb@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
	linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 1/2] acpi: support IBM SMBus CMI devices
Date: Tue, 27 Oct 2009 18:36:19 +0100	[thread overview]
Message-ID: <20091027183619.16b0b952@hyperion.delvare> (raw)
In-Reply-To: <20091027173001.GT26149@tux1.beaverton.ibm.com>

On Tue, 27 Oct 2009 10:30:01 -0700, Darrick J. Wong wrote:
> On Tue, Oct 27, 2009 at 06:03:32PM +0100, Jean Delvare wrote:
> 
> > I'm only half please with this. You change the function named, but it
> > doesn't follow the calling convention of acpi_dock_match(), which is a
> > little confusing.
> > 
> > Anyway, I will need an ack from the ACPI people before I can pick this
> > patch. Or maybe they should even push it upstream themselves.
> 
> I am confused.  Looking at that bunch of ifs, acpi_is_video_device returns 1
> for a match and 0 for no match.  acpi_bay_match returns 0 for a match and
> -ENODEV for no match, which just happens to work with the ACPI_SUCCESS macro.
> acpi_dock_match returns ACPI error codes.  Each of the three existing tests has
> different return value semantics, so it is not clear to me which one I should
> use.

Ah, sorry, I looked at one (don't remember which one) and assumed the
other ones followed the same convention.

> I didn't think it was correct for my probe function to use the ACPI_STATUS
> macro unless it returned ACPI error codes... which it does not.  -ENODEV seemed
> appropriate for "no device found".
> 
> Is it desirable to clean them all up to follow the same convention?

Ideally, yes, but that would be a separate task from what you're up to
at the moment. And anyway this is not in my realm an I am not going to
work on it myself, so my opinion probably doesn't matter that much.
Sorry for bothering you with this in the first place.

-- 
Jean Delvare

  reply	other threads:[~2009-10-27 17:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 23:11 [PATCH] i2c-scmi: Quirk to work on IBM machines with broken BIOSes Darrick J. Wong
2009-10-21  2:30 ` Crane Cai
2009-10-21 14:57   ` Bjorn Helgaas
2009-10-21 17:37     ` Darrick J. Wong
2009-10-22  7:17       ` Crane Cai
2009-10-22 17:43         ` Darrick J. Wong
2009-10-22 18:37           ` Jean Delvare
2009-10-23  4:44           ` Crane Cai
2009-10-23 17:03             ` [PATCH 1/2] i2c-scmi: support IBM SMBus CMI devices Darrick J. Wong
2009-10-25  9:39               ` Jean Delvare
2009-10-26  2:54                 ` Crane Cai
2009-10-23 17:03             ` [PATCH 2/2] acpi: " Darrick J. Wong
2009-10-25 11:53               ` Jean Delvare
2009-10-26 20:53                 ` Darrick J. Wong
2009-10-26 20:58                 ` [PATCH v2 1/2] " Darrick J. Wong
2009-10-27 17:03                   ` Jean Delvare
2009-10-27 17:30                     ` Darrick J. Wong
2009-10-27 17:36                       ` Jean Delvare [this message]
2009-12-04 17:06                         ` Darrick J. Wong
2009-12-04 17:36                           ` Bjorn Helgaas
2009-12-04 18:07                             ` Darrick J. Wong
2009-12-04 18:11                             ` [RESEND PATCH v2 1/2] ACPI: Quirk to make SMBus objects work on IBM machines with broken BIOSes Darrick J. Wong
2009-12-17 14:02                               ` Jean Delvare
2010-01-05 12:30                                 ` Jean Delvare
2009-12-04 18:13                             ` [RESEND PATCH v2 2/2] i2c-scmi: support IBM SMBus CMI devices Darrick J. Wong
2009-10-26 21:00                 ` [PATCH " Darrick J. Wong
2009-10-27 17:24                   ` 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=20091027183619.16b0b952@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=crane.cai@amd.com \
    --cc=djwong@us.ibm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.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