From: "Hawa, Hanna" <hhhawa@amazon.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: <wsa@kernel.org>, <jarkko.nikula@linux.intel.com>,
<mika.westerberg@linux.intel.com>, <jsd@semihalf.com>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dwmw@amazon.co.uk>, <benh@amazon.com>, <ronenk@amazon.com>,
<talel@amazon.com>, <jonnyc@amazon.com>, <hanochu@amazon.com>,
<farbere@amazon.com>, <itamark@amazon.com>, <lareine@amazon.com>
Subject: Re: [PATCH v3 1/1] i2c: designware: use casting of u64 in clock multiplication to avoid overflow
Date: Tue, 20 Dec 2022 18:26:05 +0200 [thread overview]
Message-ID: <c5f79b8c-a93c-d17f-3d4f-006bd4bad249@amazon.com> (raw)
In-Reply-To: <Y6GSt8AOS1nsN0dn@smile.fi.intel.com>
On 12/20/2022 12:47 PM, Andy Shevchenko wrote:
>> Fixes: 2373f6b9744d ("i2c-designware: split of i2c-designware.c into core and bus specific parts")
> It's not clear if the second patch you sent (about unsigned long --> u32) is
> required or not, can you clarify this in the changelog?
>
Sure will add to the changelog, it's not required to have the second
change to avoid the overflow.
>> Signed-off-by: Lareine Khawaly<lareine@amazon.com>
>> Signed-off-by: Hanna Hawa<hhhawa@amazon.com>
> This should be last part of the message body. The cutter '---' line makes it
> so, currently you finish your message with a changelog and not tags. So, you
> need to move the changelog after the cutter line.
Thanks for the info. will update.
>
>> Change Log v2->v3:
.
.
>> - return DIV_ROUND_CLOSEST(ic_clk * tSYMBOL, MICRO) - 8 + offset;
>> + return DIV_ROUND_CLOSEST_ULL((u64)ic_clk * tSYMBOL,
>> + MICRO) - 8 + offset;
> There is still a room for 'MICRO) -' part on the previous line.
> Ditto for the similar cases.
Ack will be fixed
prev parent reply other threads:[~2022-12-20 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 17:17 [PATCH v3 1/1] i2c: designware: use casting of u64 in clock multiplication to avoid overflow Hanna Hawa
2022-12-20 10:47 ` Andy Shevchenko
2022-12-20 16:26 ` Hawa, Hanna [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=c5f79b8c-a93c-d17f-3d4f-006bd4bad249@amazon.com \
--to=hhhawa@amazon.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benh@amazon.com \
--cc=dwmw@amazon.co.uk \
--cc=farbere@amazon.com \
--cc=hanochu@amazon.com \
--cc=itamark@amazon.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jonnyc@amazon.com \
--cc=jsd@semihalf.com \
--cc=lareine@amazon.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=ronenk@amazon.com \
--cc=talel@amazon.com \
--cc=wsa@kernel.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