From: Peter Zijlstra <peterz@infradead.org>
To: chris hyser <chris.hyser@oracle.com>
Cc: linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com,
vincent.guittot@linaro.org
Subject: Re: [PATCH] sched/numa: Fix divide by zero for sysctl_numa_balancing_scan_size.
Date: Thu, 30 Mar 2023 15:45:57 +0200 [thread overview]
Message-ID: <20230330134557.GG124812@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <d1fbf2d4-8989-effd-c908-2784f386fb8d@oracle.com>
On Wed, Mar 29, 2023 at 02:28:25PM -0400, chris hyser wrote:
> On 3/29/23 12:26, Chris Hyser wrote:
> > From: chris hyser <chris.hyser@oracle.com>
>
> Apologies. Something in my email chain put this in, but I think I figured it
> out and sent a version 1.
Not actually a problem -- all patch processing tools can deal with this
since it's a common pattern when forwarding patches written by others.
next prev parent reply other threads:[~2023-03-30 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 16:26 Chris Hyser
2023-03-29 18:28 ` chris hyser
2023-03-30 13:45 ` Peter Zijlstra [this message]
2023-03-30 15:10 ` chris hyser
2023-03-30 1:51 ` Chen Yu
2023-03-30 15:09 ` chris hyser
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=20230330134557.GG124812@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chris.hyser@oracle.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vincent.guittot@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
all inboxes | Powered by JetHome®