From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the nand tree
Date: Mon, 12 Feb 2018 23:48:39 +0100 [thread overview]
Message-ID: <20180212234839.7097af7e@bbrezillon> (raw)
In-Reply-To: <20180213093153.0958cff1@canb.auug.org.au>
On Tue, 13 Feb 2018 09:31:53 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Boris,
>
> A whole series of commits
>
> 558783726c98 ("mtd: nand: mxc: reorder functions to avoid forward declarations")
> to
> e385e291129e ("mtd: nand: mxc: remove now unused code")
>
> are missing a Signed-off-by from their committer.
>
Should be fixed now. Thanks for this report. Time for me to add an
applypatch-msg hook :-).
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-12 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 22:31 linux-next: Signed-off-by missing for commits in the nand tree Stephen Rothwell
2018-02-12 22:48 ` Boris Brezillon [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=20180212234839.7097af7e@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.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;
as well as URLs for NNTP newsgroup(s).