From: Mark Brown <broonie@kernel.org>
To: Vitor Soares <Vitor.Soares@synopsys.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"bbrezillon@kernel.org" <bbrezillon@kernel.org>,
Joao Pinto <Joao.Pinto@synopsys.com>,
"lorenzo.bianconi83@gmail.com" <lorenzo.bianconi83@gmail.com>
Subject: Re: [PATCH v2 0/3] Add ST lsm6dso i3c support
Date: Thu, 13 Jun 2019 19:38:22 +0100 [thread overview]
Message-ID: <20190613183822.GS5316@sirena.org.uk> (raw)
In-Reply-To: <13D59CF9CEBAF94592A12E8AE55501350AABEAF3@DE02WEMBXB.internal.synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
On Tue, Jun 11, 2019 at 11:42:50AM +0000, Vitor Soares wrote:
> Since the regmap-i3c.c was already applied in:
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
> tags/regmap-i3c
> I wonder what is clean way to submit this patch set?
Just mention in the cover letter that it depends on that tag, the point
with the tag is to allow other trees to pull it in if they need it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-06-13 18:38 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 ` [PATCH v2 0/3] Add ST lsm6dso i3c support Wolfram Sang
2019-06-06 16:42 ` Vitor Soares
2019-06-06 18:01 ` Wolfram Sang
2019-06-11 11:42 ` Vitor Soares
2019-06-13 18:38 ` Mark Brown [this message]
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=20190613183822.GS5316@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Joao.Pinto@synopsys.com \
--cc=Vitor.Soares@synopsys.com \
--cc=bbrezillon@kernel.org \
--cc=gregkh@linuxfoundation.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).