From: Wolfram Sang <wsa@the-dreams.de>
To: Vitor Soares <Vitor.Soares@synopsys.com>
Cc: linux-iio@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
broonie@kernel.org, gregkh@linuxfoundation.org,
rafael@kernel.org, bbrezillon@kernel.org,
Joao.Pinto@synopsys.com, lorenzo.bianconi83@gmail.com
Subject: Re: [PATCH v2 0/3] Add ST lsm6dso i3c support
Date: Thu, 6 Jun 2019 18:25:23 +0200 [thread overview]
Message-ID: <20190606162522.GA3782@kunai> (raw)
In-Reply-To: <cover.1559831663.git.vitor.soares@synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
On Thu, Jun 06, 2019 at 05:12:01PM +0200, Vitor Soares wrote:
> This patch series add i3c support for STM LSM6DSO and LSM6DSR sensors.
Why is the I2C list on CC? Is there something relevant I missed?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-06 16:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 15:12 [PATCH v2 0/3] Add ST lsm6dso i3c support Vitor Soares
2019-06-06 15:12 ` [PATCH v2 1/3] regmap: add i3c bus support Vitor Soares
2019-06-07 12:25 ` Mark Brown
2019-06-07 12:27 ` Applied "regmap: add i3c bus support" to the regmap tree Mark Brown
2019-06-06 15:12 ` [PATCH v2 2/3] i3c: add i3c_get_device_id helper Vitor Soares
2019-06-06 15:17 ` Boris Brezillon
2019-06-06 16:58 ` Vitor Soares
2019-06-06 15:12 ` [PATCH v2 3/3] iio: imu: st_lsm6dsx: add i3c basic support for LSM6DSO and LSM6DSR Vitor Soares
2019-06-06 16:58 ` Lorenzo Bianconi
2019-06-06 17:21 ` Boris Brezillon
2019-06-06 17:50 ` Lorenzo Bianconi
2019-06-06 16:25 ` Wolfram Sang [this message]
2019-06-06 16:42 ` [PATCH v2 0/3] Add ST lsm6dso i3c support Vitor Soares
2019-06-06 18:01 ` Wolfram Sang
2019-06-11 11:42 ` Vitor Soares
2019-06-13 18:38 ` Mark Brown
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=20190606162522.GA3782@kunai \
--to=wsa@the-dreams.de \
--cc=Joao.Pinto@synopsys.com \
--cc=Vitor.Soares@synopsys.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=rafael@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).