From: Wolfram Sang <wsa@the-dreams.de>
To: Phil Pokorny <ppokorny@penguincomputing.com>
Cc: Jan Glauber <jglauber@cavium.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: octeon: Prevent error message on bus error
Date: Sat, 3 Mar 2018 20:37:04 +0100 [thread overview]
Message-ID: <20180303193704.2idvbyguecpdipyl@katana> (raw)
In-Reply-To: <CAAek22H_WBejypWH=GCV7iCFCaJ46HZZ=NdPtj-iaFipqATAFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
> Did you also pick up the i2c-xlp9xx patches for current?
Dunno which one of those you mean, but I reply to every patch to which
branch I applied it to so you can check it easily.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-03-03 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 15:42 [PATCH] i2c: octeon: Prevent error message on bus error Jan Glauber
2018-03-02 10:11 ` Wolfram Sang
2018-03-02 19:19 ` Phil Pokorny
2018-03-03 19:37 ` 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=20180303193704.2idvbyguecpdipyl@katana \
--to=wsa@the-dreams.de \
--cc=jglauber@cavium.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ppokorny@penguincomputing.com \
/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).