From: Wolfram Sang <wsa@the-dreams.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 0/7 v3] I2C GPIO to use gpiolibs open drain
Date: Thu, 19 Oct 2017 16:40:19 +0200 [thread overview]
Message-ID: <20171019144019.f2mcpsida44o2ql4@katana> (raw)
In-Reply-To: <CACRpkdbjyDWFpb5p6kQTRm8Q=rM5L-Mhi4Q1rphEmOwgF6SHVg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
> Sorry to bother with this, it's fine if you don't have time
> to do the administration for this refactoring for v4.15.
My plan is to review it this weekend and hopefully merge it for v4.15.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-19 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 11:03 [PATCH 0/7 v3] I2C GPIO to use gpiolibs open drain Linus Walleij
2017-10-05 11:03 ` [PATCH 1/7 v3] i2c: gpio: Convert to use descriptors Linus Walleij
2017-10-05 11:03 ` [PATCH 2/7 v3] gpio: Make it possible for consumers to enforce open drain Linus Walleij
2017-10-05 11:03 ` [PATCH 3/7 v3] i2c: gpio: Enforce open drain through gpiolib Linus Walleij
2017-10-05 11:03 ` [PATCH 4/7 v3] i2c: gpio: Augment all boardfiles to use open drain Linus Walleij
2017-10-05 11:03 ` [PATCH 5/7 v3] i2c: gpio: Local vars in probe Linus Walleij
[not found] ` <20171005110310.5900-1-linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-10-05 11:03 ` [PATCH 6/7 v3] dt-bindings: i2c: i2c-gpio: Add support for named gpios Linus Walleij
2017-10-05 11:03 ` [PATCH 7/7 v3] i2c: gpio: Add support for named gpios in DT Linus Walleij
2017-10-19 14:37 ` [PATCH 0/7 v3] I2C GPIO to use gpiolibs open drain Linus Walleij
2017-10-19 14:40 ` Wolfram Sang [this message]
2017-10-27 13:49 ` Wolfram Sang
2017-10-30 0:28 ` Wolfram Sang
2017-10-30 7:52 ` Linus Walleij
2017-11-01 22:45 ` Wolfram Sang
2017-10-27 13:55 ` Wolfram Sang
2017-10-29 23:19 ` Linus Walleij
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=20171019144019.f2mcpsida44o2ql4@katana \
--to=wsa@the-dreams.de \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.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).