From: Richard Weinberger <richard@nod.at>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Brian Norris <computersforpeace@gmail.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the l2-mtd tree
Date: Mon, 13 Nov 2017 22:09:05 +0100 [thread overview]
Message-ID: <3708653.8v5jKD7tj3@blindfold> (raw)
In-Reply-To: <20171114080430.7c33fd83@canb.auug.org.au>
Am Montag, 13. November 2017, 22:04:30 CET schrieb Stephen Rothwell:
> Hi Brian,
>
> Commit
>
> d8c585fc5f37 ("mtd: Avoid probe failures when mtd->dbg.dfs_dir is
> invalid")
>
> is missing a Signed-off-by from its comiiter.
Fixed. :)
Thanks,
//richard
prev parent reply other threads:[~2017-11-13 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 21:04 linux-next: Signed-off-by missing for commit in the l2-mtd tree Stephen Rothwell
2017-11-13 21:09 ` Richard Weinberger [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=3708653.8v5jKD7tj3@blindfold \
--to=richard@nod.at \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.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).