From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Filipe Manana <fdmanana@suse.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the btrfs-kdave tree
Date: Tue, 5 Dec 2017 13:43:51 +0100 [thread overview]
Message-ID: <20171205124351.GG3553@suse.cz> (raw)
In-Reply-To: <20171201092250.66217bac@canb.auug.org.au>
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.
prev parent reply other threads:[~2017-12-05 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 22:22 linux-next: Signed-off-by missing for commits in the btrfs-kdave tree Stephen Rothwell
2017-12-05 12:43 ` David Sterba [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=20171205124351.GG3553@suse.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@suse.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