From: Casey Schaufler <casey@schaufler-ca.com>
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>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the smack tree
Date: Wed, 24 Jan 2024 13:37:04 -0800 [thread overview]
Message-ID: <04cd0a0a-63e6-4acb-b80e-a77e4d7d8d84@schaufler-ca.com> (raw)
In-Reply-To: <20240125083229.6bba94ec@canb.auug.org.au>
On 1/24/2024 1:32 PM, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 39fcdc643c23 ("smack: Initialize the in-memory inode in smack_inode_init_security()")
> ea2d37d1b553 ("smack: Always determine inode labels in smack_inode_init_security()")
> da5bea06bde0 ("smack: Handle SMACK64TRANSMUTE in smack_inode_setsecurity()")
> 9c5589ad9d82 ("smack: Set SMACK64TRANSMUTE only for dirs in smack_inode_setxattr()")
>
> are missing a Signed-off-by from their committer.
Bugger. Sorry, will repair.
prev parent reply other threads:[~2024-01-24 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 21:32 linux-next: Signed-off-by missing for commit in the smack tree Stephen Rothwell
2024-01-24 21:37 ` Casey Schaufler [this message]
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=04cd0a0a-63e6-4acb-b80e-a77e4d7d8d84@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--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