From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PULL REQUEST] i2c-mux for 4.15-rc1
Date: Fri, 27 Oct 2017 21:27:57 +0200 [thread overview]
Message-ID: <20171027192757.utcn6duckmfmbvi6@ninjato> (raw)
In-Reply-To: <21496b51-370f-2009-b25c-881c524fe2b9@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
Hi Peda,
> This cycle has been real quiet for me. There's only the one trivial patch
> that somewhat simplifies DT parsing in the i2c-mux-reg driver.
Did this maybe slip through the cracks?
http://patchwork.ozlabs.org/patch/816846/
("[trivial] dt-bindings: i2c: i2c-mux: Spelling s/required is/required
if/")
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-27 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 15:27 [PULL REQUEST] i2c-mux for 4.15-rc1 Peter Rosin
2017-10-26 20:26 ` Wolfram Sang
2017-10-27 19:27 ` Wolfram Sang [this message]
2017-10-27 21:05 ` Peter Rosin
2017-10-28 12:25 ` Wolfram Sang
2017-10-30 8:31 ` Peter Rosin
2017-10-30 8:39 ` 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=20171027192757.utcn6duckmfmbvi6@ninjato \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).