From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: Jan Glauber <jan.glauber@caviumnetworks.com>
Cc: "Steven J. Hill" <Steven.Hill@cavium.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, linux-mips@linux-mips.org,
Paul Burton <paul.burton@imgtec.com>,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH v2 0/3] i2c: octeon: thunder: Fix i2c not working on Octeon
Date: Mon, 28 Nov 2016 15:22:08 +0100 [thread overview]
Message-ID: <20161128142208.GA3916@katana> (raw)
In-Reply-To: <20161122145539.GA7716@hardcore>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
> > > This does not work on Octeon 71xx platforms. I will look at it more
> > > closely tomorrow.
> >
> > What's the outcome here? It seems we want a bugfix for 4.9 but this
> > report keeps me reluctant to apply the series.
> >
>
> Steven, did you have a chance to check which of the patches makes
> Octeon 71xx fail?
How do we proceed with this one? Is somebody at Cavium able to contact
Steven internally? I mentioned this on-going regression to Linus and
said an rc8 would help us, but reading LWN it seems we shouldn't count
on it...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-11-28 14:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 18:50 [PATCH v2 0/3] i2c: octeon: thunder: Fix i2c not working on Octeon Jan Glauber
2016-11-14 18:50 ` [PATCH v2 1/3] Revert "i2c: octeon: thunderx: Limit register access retries" Jan Glauber
2016-11-14 18:50 ` [PATCH v2 2/3] i2c: octeon: Fix waiting for operation completion Jan Glauber
2016-11-14 18:50 ` [PATCH v2 3/3] i2c: octeon: thunderx: TWSI software reset in recovery Jan Glauber
2016-11-14 19:53 ` [PATCH v2 0/3] i2c: octeon: thunder: Fix i2c not working on Octeon Steven J. Hill
2016-11-14 19:53 ` Steven J. Hill
2016-11-15 13:03 ` Jan Glauber
2016-11-15 13:03 ` Jan Glauber
2016-11-16 10:38 ` Paul Burton
2016-11-16 10:38 ` Paul Burton
2016-11-22 12:01 ` Wolfram Sang
2016-11-22 14:55 ` Jan Glauber
2016-11-22 14:55 ` Jan Glauber
2016-11-28 14:22 ` Wolfram Sang [this message]
2016-11-28 14:47 ` Steven J. Hill
2016-11-28 14:47 ` Steven J. Hill
2016-11-29 9:19 ` Jan Glauber
2016-11-29 9:19 ` Jan Glauber
2016-11-29 18:22 ` Steven J. Hill
2016-11-29 18:22 ` Steven J. Hill
2016-11-29 18:37 ` Wolfram Sang
2016-11-29 19:10 ` Steven J. Hill
2016-11-29 19:10 ` Steven J. Hill
2016-11-29 19:14 ` 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=20161128142208.GA3916@katana \
--to=wsa-dev@sang-engineering.com \
--cc=Steven.Hill@cavium.com \
--cc=david.daney@cavium.com \
--cc=jan.glauber@caviumnetworks.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.