linux-kernel - Re: linux-next: Signed-off-by missing for commits in the btrfs-kdave tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20171205124351.GG3553@suse.cz>
Date:   Tue, 5 Dec 2017 13:43:51 +0100
From:   David Sterba <dsterba@...e.cz>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Filipe Manana <fdmanana@...e.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the btrfs-kdave
 tree

On Fri, Dec 01, 2017 at 09:22:49AM +1100, Stephen Rothwell wrote:
> Hi David,
> 
> Commits
> 
>   f212bed55c85 ("Btrfs: add support for fallocate's zero range operation")
>   2d0d54302a5f ("Btrfs: use cached state when dirtying pages during buffered write")
> 
> are missing a Signed-off-by from their committer.

Will be fixed in the next for-next version.

This was caused by rebasing a branch that's normally merged to for-next.
Some of the patches have been merged to master and caused conflicts.