From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Theodore Ts'o <tytso@mit•edu>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
brookxu <brookxu.cn@gmail•com>,
Chunguang Xu <brookxu@tencent•com>
Subject: linux-next: Signed-off-by missing for commits in the ext4 tree
Date: Wed, 19 Aug 2020 08:30:34 +1000 [thread overview]
Message-ID: <20200819083034.6c2b3b33@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
Hi all,
Commits
dddcd2f9ebde ("ext4: optimize the implementation of ext4_mb_good_group()")
051e2ce8cb90 ("ext4: delete invalid comments near ext4_mb_check_limits()")
e9a3cd48d653 ("ext4: fix typos in ext4_mb_regular_allocator() comment")
9375ac770cda ("ext4: delete the invalid BUGON in ext4_mb_load_buddy_gfp()")
are missing a Signed-off-by from their authors.
Not really (I assume), but their author is brookxu <brookxu.cn@gmail•com>
and the Signed-off-by is Chunguang Xu <brookxu@tencent•com>. Consistency
would be nice.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2020-08-18 22:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200819083034.6c2b3b33@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=brookxu.cn@gmail$(echo .)com \
--cc=brookxu@tencent$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tytso@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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