From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] ARM: pxa: stargate2: use device properties for at24 eeprom
Date: Sun, 08 Apr 2018 11:03:48 +0200 [thread overview]
Message-ID: <87sh862hor.fsf@belgarion.home> (raw)
In-Reply-To: <CAMRc=MfD659sqbwRJs2tti-VcSShLWU-yB8=SR7zhv8Pz6XQcA@mail.gmail.com> (Bartosz Golaszewski's message of "Thu, 5 Apr 2018 10:32:38 +0200")
Bartosz Golaszewski <brgl@bgdev.pl> writes:
> 2018-04-04 21:44 GMT+02:00 Robert Jarzmik <robert.jarzmik@free.fr>:
>> Bartosz Golaszewski <brgl@bgdev.pl> writes:
> Yes, it does use the type field from i2c_board_info implicitly over
> i2c-core. The type field is copied over to client->name and then is
> matched against the i2c ID table from which we get the associated chip
> data (unless the type is "at24") containing the size and flags.
Ah yes, the "struct i2c_device_id at24_ids" part, I see.
Applied to pxa/for-next, thanks.
--
Robert
WARNING: multiple messages have this Message-ID (diff)
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH] ARM: pxa: stargate2: use device properties for at24 eeprom
Date: Sun, 08 Apr 2018 11:03:48 +0200 [thread overview]
Message-ID: <87sh862hor.fsf@belgarion.home> (raw)
In-Reply-To: <CAMRc=MfD659sqbwRJs2tti-VcSShLWU-yB8=SR7zhv8Pz6XQcA@mail.gmail.com> (Bartosz Golaszewski's message of "Thu, 5 Apr 2018 10:32:38 +0200")
Bartosz Golaszewski <brgl@bgdev.pl> writes:
> 2018-04-04 21:44 GMT+02:00 Robert Jarzmik <robert.jarzmik@free.fr>:
>> Bartosz Golaszewski <brgl@bgdev.pl> writes:
> Yes, it does use the type field from i2c_board_info implicitly over
> i2c-core. The type field is copied over to client->name and then is
> matched against the i2c ID table from which we get the associated chip
> data (unless the type is "at24") containing the size and flags.
Ah yes, the "struct i2c_device_id at24_ids" part, I see.
Applied to pxa/for-next, thanks.
--
Robert
next prev parent reply other threads:[~2018-04-08 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 11:47 [RESEND PATCH] ARM: pxa: stargate2: use device properties for at24 eeprom Bartosz Golaszewski
2018-04-04 11:47 ` Bartosz Golaszewski
2018-04-04 12:08 ` Jonathan Cameron
2018-04-04 12:08 ` Jonathan Cameron
2018-04-04 19:44 ` Robert Jarzmik
2018-04-04 19:44 ` Robert Jarzmik
2018-04-05 8:32 ` Bartosz Golaszewski
2018-04-05 8:32 ` Bartosz Golaszewski
2018-04-08 9:03 ` Robert Jarzmik [this message]
2018-04-08 9:03 ` Robert Jarzmik
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=87sh862hor.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.