From: Wolfram Sang <wsa@the-dreams.de>
To: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
Cc: Zhangfei Gao <zhangfei.gao@linaro.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Luis.Oliveira@synopsys.com
Subject: Re: [PATCH v3 resend] i2c: designware: add reset interface
Date: Thu, 9 Mar 2017 15:43:40 +0100 [thread overview]
Message-ID: <20170309144340.pp4pu7a272kmsjdm@ninjato> (raw)
In-Reply-To: <381cd2c0-499d-884a-3c4e-6fedc422f2e0@synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Mon, Mar 06, 2017 at 03:11:48PM +0000, Ramiro Oliveira wrote:
> Hi Wolfram
>
> On 1/12/2017 6:54 PM, Wolfram Sang wrote:
> > On Tue, Dec 27, 2016 at 10:22:40PM +0800, Zhangfei Gao wrote:
> >> Some platforms like hi3660 need do reset first to allow accessing registers
> >>
> >> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
> >> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >> Tested-by: Ramiro Oliveira <ramiro.oliveira@synopsys.com>
> >
> > Applied to for-next, thanks!
> >
>
> I haven't been able to find this patch anywhere. Do you still have plans to
> apply it to for-next?
Uh, thanks for the heads up. Can't really tell why it fell through the
cracks :( It probably got lost by an improper rebase by me? Sorry about
that.
Applied to for-current, thanks again!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-03-09 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 14:22 [PATCH v3 resend] i2c: designware: add reset interface Zhangfei Gao
2016-12-27 14:41 ` Jarkko Nikula
2017-01-12 18:54 ` Wolfram Sang
2017-03-06 15:11 ` Ramiro Oliveira
2017-03-09 14:43 ` 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=20170309144340.pp4pu7a272kmsjdm@ninjato \
--to=wsa@the-dreams.de \
--cc=Luis.Oliveira@synopsys.com \
--cc=Ramiro.Oliveira@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=p.zabel@pengutronix.de \
--cc=zhangfei.gao@linaro.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