From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Kir Kolyshkin <kolyshkin@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the jc_docs tree
Date: Fri, 22 Jan 2021 07:57:47 +1100 [thread overview]
Message-ID: <20210122075747.3622cd8e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
Hi all,
In commit
cf9cadf16b19 ("docs/admin-guide: cgroup-v2: typos and spaces")
Fixes tag
Fixes: 5f9a4f4a70960
has these problem(s):
- missing subject
Maybe you meant
Fixes: 5f9a4f4a7096 ("mm: memcontrol: add the missing numa_stat interface for cgroup v2")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-01-21 21:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 20:57 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-03 23:46 linux-next: Fixes tag needs some work in the jc_docs tree Stephen Rothwell
2023-07-04 14:32 ` Jonathan Corbet
2023-07-03 21:54 Stephen Rothwell
2022-03-28 20:58 Stephen Rothwell
2022-01-06 23:36 Stephen Rothwell
2022-01-07 10:25 ` James Clark
2022-01-07 16:19 ` Randy Dunlap
2022-01-10 10:30 ` James Clark
2022-01-07 16:35 ` Jonathan Corbet
2021-02-25 21:34 Stephen Rothwell
2021-02-25 21:39 ` Jonathan Corbet
2021-02-25 22:01 ` Stephen Rothwell
2021-02-25 22:35 ` Andrew Donnellan
2019-05-20 21:44 Stephen Rothwell
2019-05-20 21:54 ` Jonathan Corbet
2019-05-21 7:18 ` Sven Eckelmann
2019-05-21 15:31 ` Jonathan Corbet
2019-05-21 18:23 ` Sven Eckelmann
2019-05-21 18:46 ` Jonathan Corbet
2019-05-21 18:52 ` Sven Eckelmann
2019-05-21 19:04 ` Jonathan Corbet
2019-05-21 19:05 ` Sven Eckelmann
2019-05-21 7:12 ` Sven Eckelmann
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=20210122075747.3622cd8e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=corbet@lwn.net \
--cc=kolyshkin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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.