The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Serge Semin <fancer.lancer@gmail.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Wei Yongjun <weiyongjun1@huawei.com>,
	Julia Lawall <julia.lawall@lip6.fr>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Colin Ian King <colin.king@canonical.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v2 3/3] eeprom: idt_89hpesx: Add OF device ID table
Date: Tue, 21 Mar 2017 17:52:50 +0300	[thread overview]
Message-ID: <20170321145250.GA29906@mobilestation> (raw)
In-Reply-To: <20170321135049.16211-3-javier@osg.samsung.com>

On Tue, Mar 21, 2017 at 10:50:49AM -0300, Javier Martinez Canillas <javier@osg.samsung.com> wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
> that the MODALIAS reported will always be of the form i2c:<device>.
> 
> But this could change in the future so the correct approach is to have an
> OF device ID table if the devices are registered via OF.
> 
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>

Acked-by: Serge Semin <fancer.lancer@gmail.com>

  parent reply	other threads:[~2017-03-21 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 13:50 [PATCH v2 1/3] misc: tsl2550: Add OF device ID table Javier Martinez Canillas
2017-03-21 13:50 ` [PATCH v2 2/3] misc: ds1682: " Javier Martinez Canillas
2017-03-21 13:54   ` Arnd Bergmann
2017-03-21 13:50 ` [PATCH v2 3/3] eeprom: idt_89hpesx: " Javier Martinez Canillas
2017-03-21 13:54   ` Arnd Bergmann
2017-03-21 14:52   ` Serge Semin [this message]
2017-03-21 13:54 ` [PATCH v2 1/3] misc: tsl2550: " Arnd Bergmann

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=20170321145250.GA29906@mobilestation \
    --to=fancer.lancer@gmail.com \
    --cc=arnd@arndb.de \
    --cc=colin.king@canonical.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=javier@osg.samsung.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weiyongjun1@huawei.com \
    /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