linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Adrian Freund <adrian@freund.io>
Cc: linux-doc@vger.kernel.org, peterz@infradead.org
Subject: Re: [PATCH] Documentation: scheduler: fix outdated information on sched groups
Date: Tue, 21 Apr 2020 13:38:31 -0600	[thread overview]
Message-ID: <20200421133831.4506c64c@lwn.net> (raw)
In-Reply-To: <20200407130525.76663-1-adrian@freund.io>

On Tue,  7 Apr 2020 15:05:25 +0200
Adrian Freund <adrian@freund.io> wrote:

> The documentation claims that two sched groups must not overlap. This is
> no longer true, as overlapping sched groups are used on NUMA systems.
> This change has been introduced by commit e3589f6c81e47 and was
> documented by an in-code comment in commit 35a566e6e8a18.
> 
> Signed-off-by: Adrian Freund <adrian@freund.io>

In the absence of complaints from Peter, I've gone ahead and applied this.

Thanks,

jon

      reply	other threads:[~2020-04-21 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 13:05 [PATCH] Documentation: scheduler: fix outdated information on sched groups Adrian Freund
2020-04-21 19:38 ` Jonathan Corbet [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=20200421133831.4506c64c@lwn.net \
    --to=corbet@lwn.net \
    --cc=adrian@freund.io \
    --cc=linux-doc@vger.kernel.org \
    --cc=peterz@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;
as well as URLs for NNTP newsgroup(s).