From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: Stefan Roesch <shr@devkernel.io>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
joseph.qi@linux.alibaba.com, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org, willy@infradead.org
Subject: Re: [PATCH v3 0/2] mm: fix arithmetic for bdi min_ratio and max_ratio
Date: Wed, 20 Dec 2023 09:43:47 +0800 [thread overview]
Message-ID: <9f11d308-54a8-4152-9da7-90a49de8d5e0@linux.alibaba.com> (raw)
In-Reply-To: <79e0cb77-ea6a-427f-af5e-c1762049ac89@app.fastmail.com>
On 12/20/23 1:56 AM, Stefan Roesch wrote:
> It would be good if the cover letter describes what this fixes.
Thanks. Would notice that next time :)
>
> On Tue, Dec 19, 2023, at 6:25 AM, Jingbo Xu wrote:
>> changes since v2:
>> - patch 2: drop div64_u64(), instead write it out mathematically
>> (Matthew Wilcox)
>>
>> changes since v1:
>> - split the previous v1 patch into two separate patches with
>> corresponding "Fixes" tag (Andrew Morton)
>> - patch 2: remove "UL" suffix for the "100" constant
>>
>> v1:
>> https://lore.kernel.org/all/20231218031640.77983-1-jefflexu@linux.alibaba.com/
>> v2:
>> https://lore.kernel.org/all/20231219024246.65654-1-jefflexu@linux.alibaba.com/
>>
>> Jingbo Xu (2):
>> mm: fix arithmetic for bdi min_ratio
>> mm: fix arithmetic for max_prop_frac when setting max_ratio
>>
>> mm/page-writeback.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> --
>> 2.19.1.6.gb485710b
--
Thanks,
Jingbo
prev parent reply other threads:[~2023-12-20 1:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:25 Jingbo Xu
2023-12-19 14:25 ` [PATCH v3 1/2] mm: fix arithmetic for bdi min_ratio Jingbo Xu
2024-01-04 17:33 ` Jan Kara
2023-12-19 14:25 ` [PATCH v3 2/2] mm: fix arithmetic for max_prop_frac when setting max_ratio Jingbo Xu
2024-01-04 17:41 ` Jan Kara
2023-12-19 17:56 ` [PATCH v3 0/2] mm: fix arithmetic for bdi min_ratio and max_ratio Stefan Roesch
2023-12-20 1:43 ` Jingbo Xu [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=9f11d308-54a8-4152-9da7-90a49de8d5e0@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shr@devkernel.io \
--cc=willy@infradead.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