public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: I2C algorithm IDs
Date: Mon, 31 Jan 2005 23:19:03 -0800	[thread overview]
Message-ID: <20050201071903.GG20783@kroah.com> (raw)
In-Reply-To: <20050122174718.A27993@flint.arm.linux.org.uk>

On Sat, Jan 22, 2005 at 05:47:18PM +0000, Russell King wrote:
> Greg,
> 
> Are I2C algorithm IDs supposed to be unique?  Do they have any meaning in
> reality at all?  If the answer is yes to either of these questions, the
> following should probably be resolved:

Yes, they are used in some places, and yes they do need to be unique.

> #define I2C_ALGO_PCA    0x150000        /* PCA 9564 style adapters      */
> #define I2C_ALGO_SIBYTE 0x150000        /* Broadcom SiByte SOCs         */

Thanks for pointing this out, I've gone and fixed this up and will send
the patch upward.

thanks,

greg k-h

      reply	other threads:[~2005-02-01  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-22 17:47 I2C algorithm IDs Russell King
2005-02-01  7:19 ` Greg KH [this message]

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=20050201071903.GG20783@kroah.com \
    --to=greg@kroah.com \
    --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