From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yunlei He <heyunlei@huawei.com>, Chao Yu <yuchao0@huawei.com>
Subject: linux-next: Signed-off-by missing for commit in the f2fs tree
Date: Mon, 13 Nov 2017 07:39:58 +1100 [thread overview]
Message-ID: <20171113073958.6e63ed70@canb.auug.org.au> (raw)
Hi Jaegeuk,
Commit
c79d88f915ed ("f2fs: separate nat entry mem alloc from nat_tree_lock")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-11-12 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 20:39 Stephen Rothwell [this message]
2017-11-14 2:29 ` linux-next: Signed-off-by missing for commit in the f2fs tree Jaegeuk Kim
2019-06-26 23:55 Stephen Rothwell
2019-06-27 0:43 ` Jaegeuk Kim
2020-03-10 9:58 Stephen Rothwell
2020-03-10 16:17 ` Jaegeuk Kim
2020-04-16 22:17 Stephen Rothwell
2020-04-16 23:18 ` Jaegeuk Kim
2022-06-13 22:15 Stephen Rothwell
2022-06-14 0:06 ` Jaegeuk Kim
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=20171113073958.6e63ed70@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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).