From: Wolfram Sang <wsa@the-dreams.de>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: "wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"kieran.bingham+renesas@ideasonboard.com"
<kieran.bingham+renesas@ideasonboard.com>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"peda@axentia.se" <peda@axentia.se>,
Support Opensource <Support.Opensource@diasemi.com>
Subject: Re: [PATCH] mfd: da9063: occupy second I2C address, too
Date: Fri, 21 Jun 2019 12:09:59 +0200 [thread overview]
Message-ID: <20190621100959.GA2568@kunai> (raw)
In-Reply-To: <AM6PR10MB218134CDB4ECB0A9534B6B96FEE70@AM6PR10MB2181.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
> For what it's worth, maybe consider adding a dev_warn attached to the return
> of devm_i2c_new_dummy_device?
I am in the middle of some API changes. Once those are over, I want to
think about such warnings as a second step. I'd rather have them in the
core than in each and every driver. But this needs more thinking...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-21 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 9:07 [PATCH] mfd: da9063: occupy second I2C address, too Steve Twiss
2019-06-20 9:21 ` Wolfram Sang
2019-06-21 9:23 ` Steve Twiss
2019-06-21 10:09 ` Wolfram Sang [this message]
2019-06-21 10:23 ` Steve Twiss
2019-06-20 12:28 ` Lee Jones
2019-06-20 12:44 ` Steve Twiss
2019-06-20 13:33 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2025-06-01 11:22 Wolfram Sang
2025-06-13 14:06 ` Lee Jones
2025-06-13 14:06 ` Lee Jones
2019-06-19 17:18 Wolfram Sang
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=20190621100959.GA2568@kunai \
--to=wsa@the-dreams.de \
--cc=Support.Opensource@diasemi.com \
--cc=bgolaszewski@baylibre.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=peda@axentia.se \
--cc=stwiss.opensource@diasemi.com \
--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.