From: "Darrick J. Wong" <djwong@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the xfs tree
Date: Wed, 11 Aug 2021 12:21:35 -0700 [thread overview]
Message-ID: <20210811192135.GU3601466@magnolia> (raw)
In-Reply-To: <20210811074913.48605817@canb.auug.org.au>
On Wed, Aug 11, 2021 at 07:49:13AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 0f3901673631 ("xfs: Rename __xfs_attr_rmtval_remove")
> da8ca45da62e ("xfs: add attr state machine tracepoints")
>
> are missing a Signed-off-by from their committer.
These should be fixed in today's for-next branch; thanks for letting me
know.
I have also spent this morning fixing some logic errors in my checkpatch
script (which basically does the same as the ones you sent me last time
this happened) and correcting a bug in the pre-push hook that resulted
in it not running. :/
--D
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2021-08-11 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 21:49 linux-next: Signed-off-by missing for commits in the xfs tree Stephen Rothwell
2021-08-11 19:21 ` Darrick J. Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-20 22:26 Stephen Rothwell
2021-06-21 17:12 ` 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
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=20210811192135.GU3601466@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).