From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org, Leon Romanovsky <leon@leon.nu>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2] i2c: mux: only print failure message on error
Date: Mon, 15 May 2017 11:31:20 +0200 [thread overview]
Message-ID: <20170515093120.GA2834@tetsubishi> (raw)
In-Reply-To: <1494834017-24678-1-git-send-email-peda@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
> Wolfram, you can take this one directly if you wish. You can also
> take [1] (and optionally [2]) directly if you wish. Or just holler
> and I'll send you a pull request with [1] and this patch for-current.
Frankly, I'd prefer a pull-request. Less chances that I mix up things
for patches which I don't really follow because I entrust them to you :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-05-15 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 7:40 [PATCH v2] i2c: mux: only print failure message on error Peter Rosin
2017-05-15 9:31 ` Wolfram Sang [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=20170515093120.GA2834@tetsubishi \
--to=wsa@the-dreams.de \
--cc=leon@leon.nu \
--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).