From: Andrew Jeffery <andrew@aj.id.au>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, brendanhiggins@google.com,
benh@kernel.crashing.org, joel@jms.id.au,
openbmc@lists.ozlabs.org, linux-aspeed@lists.ozlabs.org,
linux-kernel@vger.kernel.org, ryan_chen@aspeedtech.com
Subject: Re: [PATCH] i2c: aspeed: Retain delay/setup/hold values when configuring bus frequency
Date: Tue, 29 Aug 2017 18:16:29 +0930 [thread overview]
Message-ID: <1503996389.5933.9.camel@aj.id.au> (raw)
In-Reply-To: <20170829084508.edybxf6zctgx4xwy@ninjato>
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
On Tue, 2017-08-29 at 10:45 +0200, Wolfram Sang wrote:
> > I'd argue that Brendan's patch should go in for-current as well,
> > because it fixes a divisor rounding error for the ast2500 (bus is
> > clocked faster than requested).
>
> Hmmm, pity, the description said "potential" issue so I decided for
> for-next. However, I wouldn't like to reshuffle my branches much so
> short before the merge window. So, would it be OK with you that you send
> both patches to stable after rc1?
>
Will do.
Cheers,
Andrew
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2017-08-29 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 7:21 [PATCH] i2c: aspeed: Retain delay/setup/hold values when configuring bus frequency Andrew Jeffery
2017-08-16 6:30 ` Brendan Higgins
2017-08-16 6:49 ` Joel Stanley
2017-08-16 6:53 ` Cédric Le Goater
2017-08-16 6:59 ` Benjamin Herrenschmidt
2017-08-16 7:15 ` Cédric Le Goater
2017-08-24 0:19 ` Brendan Higgins
2017-08-28 16:07 ` Wolfram Sang
2017-08-29 6:56 ` Andrew Jeffery
2017-08-29 8:45 ` Wolfram Sang
2017-08-29 8:46 ` Andrew Jeffery [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=1503996389.5933.9.camel@aj.id.au \
--to=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=brendanhiggins@google.com \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=ryan_chen@aspeedtech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox