From: Steve Twiss <stwiss.opensource@diasemi.com>
To: Lee Jones <lee.jones@linaro.org>,
"wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>
Cc: "bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"kieran.bingham+renesas@ideasonboard.com"
<kieran.bingham+renesas@ideasonboard.com>,
"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: Thu, 20 Jun 2019 12:44:50 +0000 [thread overview]
Message-ID: <AM6PR10MB2181D2A08D98FB9F8092EC8DFEE40@AM6PR10MB2181.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20190620122853.GD4699@dell>
On 20 June 2019 13:29, Lee Jones wrote:
> Subject: Re: [PATCH] mfd: da9063: occupy second I2C address, too
>
> Why isn't this reply attached (threaded) to the patch.
My apologies. It wasn't my intention to split Wolfram's original e-mail thread.
I don't usually reply using the mailto: link from lore when creating e-mails.
Outlook mustn't support the In-Reply-To header.
I'll figure out a different way to reply in future.
> Is your mailer broken?
It's Windows
next prev parent reply other threads:[~2019-06-20 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 9:07 Steve Twiss
2019-06-20 9:21 ` Wolfram Sang
2019-06-21 9:23 ` Steve Twiss
2019-06-21 10:09 ` Wolfram Sang
2019-06-21 10:23 ` Steve Twiss
2019-06-20 12:28 ` Lee Jones
2019-06-20 12:44 ` Steve Twiss [this message]
2019-06-20 13:33 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
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=AM6PR10MB2181D2A08D98FB9F8092EC8DFEE40@AM6PR10MB2181.EURPRD10.PROD.OUTLOOK.COM \
--to=stwiss.opensource@diasemi.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®