From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Darrick J. Wong" <djwong@kernel.org>,
David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org
Cc: Allison Henderson <allison.henderson@oracle.com>,
Chandan Babu R <chandanrlinux@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commits in the xfs tree
Date: Mon, 21 Jun 2021 08:26:56 +1000 [thread overview]
Message-ID: <20210621082656.59cae0d8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Hi all,
Commits
742140d2a486 ("xfs: xfs_log_force_lsn isn't passed a LSN")
e30fbb337045 ("xfs: Fix CIL throttle hang when CIL space used going backwards")
feb616896031 ("xfs: journal IO cache flush reductions")
6a5c6f5ef0a4 ("xfs: remove need_start_rec parameter from xlog_write()")
d7693a7f4ef9 ("xfs: CIL checkpoint flushes caches unconditionally")
e45cc747a6fd ("xfs: async blkdev cache flush")
9b845604a4d5 ("xfs: remove xfs_blkdev_issue_flush")
25f25648e57c ("xfs: separate CIL commit record IO")
a6a65fef5ef8 ("xfs: log stripe roundoff is a property of the log")
are missing a Signed-off-by from their committers.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-20 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 22:26 Stephen Rothwell [this message]
2021-06-21 17:12 ` linux-next: Signed-off-by missing for commits in the xfs tree Darrick J. Wong
2021-06-21 21:27 ` Stephen Rothwell
2021-06-21 21:51 ` Darrick J. Wong
2021-06-21 22:10 ` Stephen Rothwell
2021-06-21 23:06 ` Stephen Rothwell
2021-06-21 21:54 ` Dave Chinner
2021-08-10 21:49 Stephen Rothwell
2021-08-11 19:21 ` Darrick J. Wong
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=20210621082656.59cae0d8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=allison.henderson@oracle.com \
--cc=chandanrlinux@gmail.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@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 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).