From: Jeff Layton <jlayton@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 commit in the file-locks tree
Date: Wed, 08 Mar 2023 18:21:29 -0500 [thread overview]
Message-ID: <baff7de11dca4b429d2f4316775c6227d9c01576.camel@kernel.org> (raw)
In-Reply-To: <20230309084800.58ec0343@canb.auug.org.au>
On Thu, 2023-03-09 at 08:48 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 4cbb75d0fdc9 ("fs/locks: Remove redundant assignment to cmd")
>
> is missing a Signed-off-by from its committer.
>
Good catch, thanks. It should be fixed now.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-03-08 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 21:48 linux-next: Signed-off-by missing for commit in the file-locks tree Stephen Rothwell
2023-03-08 23:21 ` Jeff Layton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-23 22:45 Stephen Rothwell
2023-07-23 23:47 ` Jeff Layton
2020-03-14 12:47 Stephen Rothwell
2020-03-11 14:18 Stephen Rothwell
2020-03-11 20:06 ` Jeff Layton
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=baff7de11dca4b429d2f4316775c6227d9c01576.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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