From: Thomas Gleixner <tglx@linutronix.de>
To: tip-bot2 for Nicholas Piggin <tip-bot2@linutronix.de>,
linux-tip-commits@vger.kernel.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [tip: sched/core] sched/wait_bit, mm/filemap: Increase page and bit waitqueue hash size
Date: Wed, 17 Mar 2021 16:16:46 +0100 [thread overview]
Message-ID: <87v99pyfmp.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <161598470782.398.7078277215554525953.tip-bot2@tip-bot2>
On Wed, Mar 17 2021 at 12:38, tip-bot wrote:
> The following commit has been merged into the sched/core branch of tip:
>
> Commit-ID: 873d7c4c6a920d43ff82e44121e54053d4edba93
> Gitweb: https://git.kernel.org/tip/873d7c4c6a920d43ff82e44121e54053d4edba93
> Author: Nicholas Piggin <npiggin@gmail.com>
> AuthorDate: Wed, 17 Mar 2021 17:54:27 +10:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Wed, 17 Mar 2021 09:32:30 +01:00
Groan. This does not even compile and Nicholas already sent a V3 in the
very same thread. Zapped ...
next prev parent reply other threads:[~2021-03-17 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 7:54 [PATCH v2] Increase page and bit waitqueue hash size Nicholas Piggin
2021-03-17 8:38 ` Ingo Molnar
2021-03-17 10:02 ` Nicholas Piggin
2021-03-17 10:12 ` Rasmus Villemoes
2021-03-17 10:44 ` Nicholas Piggin
2021-03-17 19:26 ` Linus Torvalds
2021-03-17 22:22 ` Nicholas Piggin
2021-03-17 23:13 ` Linus Torvalds
2021-03-17 11:25 ` kernel test robot
2021-03-17 11:25 ` kernel test robot
2021-03-17 11:30 ` kernel test robot
2021-03-17 11:30 ` kernel test robot
2021-03-17 12:38 ` [tip: sched/core] sched/wait_bit, mm/filemap: " tip-bot2 for Nicholas Piggin
2021-03-17 15:16 ` Thomas Gleixner [this message]
2021-03-17 19:54 ` Ingo Molnar
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=87v99pyfmp.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=tip-bot2@linutronix.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.