From: Wolfram Sang <wsa@the-dreams.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Kieran Bingham <kieran@ksquared.org.uk>
Subject: Re: [PATCH v7 0/3] i2c: improve i2c_new_{device|dummy}
Date: Wed, 13 Mar 2019 22:09:24 +0100 [thread overview]
Message-ID: <20190313210924.GB3480@kunai> (raw)
In-Reply-To: <CAMRc=Mc85U_WmY1RCNMCwMPJoO2jwYxvOaNiBNbuBaigJnoaqg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 172 bytes --]
> Wasn't there a patch using this new managed variant in at24 as well?
My Lager board has no EEPROM, so I skipped that. I was more interested
in the core parts for now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-13 21:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 16:55 [PATCH v7 0/3] i2c: improve i2c_new_{device|dummy} Wolfram Sang
2019-03-13 16:55 ` [PATCH v7 1/3] i2c: core: improve return value handling of i2c_new_device and i2c_new_dummy Wolfram Sang
2019-03-15 11:57 ` Simon Horman
2019-03-15 12:15 ` Kieran Bingham
2019-03-13 16:55 ` [PATCH v7 2/3] i2c: core: add device-managed version of i2c_new_dummy Wolfram Sang
2019-03-14 10:25 ` Peter Rosin
2019-03-15 12:06 ` Kieran Bingham
2019-03-15 21:08 ` Wolfram Sang
2019-03-16 8:21 ` Peter Rosin
2019-03-16 16:44 ` Wolfram Sang
2019-03-16 16:43 ` Wolfram Sang
2019-03-17 21:32 ` Peter Rosin
2019-03-15 12:05 ` Simon Horman
2019-03-13 16:55 ` [PATCH v7 3/3] mfd: da9063: occupy second I2C address, too Wolfram Sang
2019-03-15 12:06 ` Simon Horman
2019-03-13 20:55 ` [PATCH v7 0/3] i2c: improve i2c_new_{device|dummy} Bartosz Golaszewski
2019-03-13 21:09 ` Wolfram Sang [this message]
2019-03-13 21:18 ` Bartosz Golaszewski
2019-03-13 21:19 ` Wolfram Sang
2019-03-14 8:51 ` Bartosz Golaszewski
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=20190313210924.GB3480@kunai \
--to=wsa@the-dreams.de \
--cc=brgl@bgdev.pl \
--cc=hkallweit1@gmail.com \
--cc=kieran@ksquared.org.uk \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 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.