From: Wolfram Sang <wsa@the-dreams.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: devicetree <devicetree@vger.kernel.org>,
qii.wang@mediatek.com,
srv_heupstream <srv_heupstream@mediatek.com>,
Leilk Liu <leilk.liu@mediatek.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] i2c: mediatek: Fix generic definitions for bus frequencies
Date: Fri, 18 Sep 2020 22:45:35 +0200 [thread overview]
Message-ID: <20200918204535.GA52206@kunai> (raw)
In-Reply-To: <CAHp75VeBuR4fkVk0z=+d7EonHz0h=4=eRj3Wfe8R_8T=eyHaeA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 365 bytes --]
> > - if (target_speed > I2C_MAX_FAST_MODE_PLUS_FREQ)
> > - target_speed = I2C_MAX_FAST_MODE_PLUS_FREQ;
> > + if (target_speed > I2C_MAX_HIGH_SPEED_MODE_FREQ)
> > + target_speed = I2C_MAX_HIGH_SPEED_MODE_FREQ;
>
> Thanks for fixing this. Indeed, somehow I messed these up.
I read this as Rev-by for v2. Thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-18 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 5:57 [PATCH] i2c: mediatek: Fix generic definitions for bus frequencies qii.wang
2020-09-13 15:15 ` Yingjoe Chen
2020-09-14 12:48 ` Andy Shevchenko
2020-09-15 1:24 ` Qii Wang
2020-09-18 20:45 ` 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=20200918204535.GA52206@kunai \
--to=wsa@the-dreams.de \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=leilk.liu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=qii.wang@mediatek.com \
--cc=srv_heupstream@mediatek.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).