From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: jic23@jic23.retrosnub.co.uk, Jonathan Cameron <jic23@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-iio@vger.kernel.org, Nick Vaccaro <nvaccaro@google.com>,
Ge Gao <ggao@invensense.com>, Anna Si <asi@invensense.com>,
Nathan Royer <nroyer@invensense.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Crestez Dan Leonard <leonard.crestez@intel.com>,
Daniel Baluta <daniel.baluta@intel.com>,
Gregor Boirie <gregor.boirie@parrot.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 2/2] iio: gyro: Add driver for the MPU-3050 gyroscope
Date: Wed, 24 Aug 2016 13:50:58 +0200 [thread overview]
Message-ID: <20160824115058.GA5190@katana> (raw)
In-Reply-To: <ed7493a1-37e4-2291-c66e-11cb97b6e5e3@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
> Wolfram, is that ok with you? Or should I just bite the bullet and ask
> Stephen to include a brand new for-next branch from the i2c-mux repo
> instead?
I had a glimpse of the series in question and it looks good to me. Looks
like I'll pull it in today or tomorrow.
But it may be nice to have a branch in your mux-repo that people can
pull anyhow? I usually don't like pulling all of linux-next when I only
want one specific feature.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-24 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1471286287-25074-1-git-send-email-linus.walleij@linaro.org>
[not found] ` <53008712-7c50-79db-07ab-3544902887e1@kernel.org>
[not found] ` <285e7c3f-eedb-28ed-f651-926260d17a8a@axentia.se>
[not found] ` <c45a4c34d8c980d20e790741f33961f7@jic23.retrosnub.co.uk>
[not found] ` <c45a4c34d8c980d20e790741f33961f7-tko9wxEg+fIOOJlXag/Snyp2UmYkHbXO@public.gmane.org>
2016-08-24 8:49 ` [PATCH 2/2] iio: gyro: Add driver for the MPU-3050 gyroscope Peter Rosin
2016-08-24 11:50 ` Wolfram Sang [this message]
[not found] ` <CACRpkdZeomin6_u=1hm-fJucMnQmAJXu01YaC0g1KdafWPD2kg@mail.gmail.com>
2016-08-25 20:32 ` Peter Rosin
2016-08-25 22:52 ` Wolfram Sang
[not found] ` <5903e282-aaf9-9c86-5df5-17b75d5b4018-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-08-26 7:39 ` Linus Walleij
2016-08-29 17:41 ` Jonathan Cameron
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=20160824115058.GA5190@katana \
--to=wsa@the-dreams.de \
--cc=asi@invensense.com \
--cc=daniel.baluta@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ggao@invensense.com \
--cc=gregor.boirie@parrot.com \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=jic23@kernel.org \
--cc=leonard.crestez@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=nroyer@invensense.com \
--cc=nvaccaro@google.com \
--cc=peda@axentia.se \
/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).