From: Zhang Rui <rui.zhang@intel.com>
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>
Subject: Re: linux-next: Signed-off-bys missing for commits in the thermal tree
Date: Tue, 05 Sep 2017 09:15:04 +0800 [thread overview]
Message-ID: <1504574104.3022.1.camel@intel.com> (raw)
In-Reply-To: <20170905105734.13e4c3cc@canb.auug.org.au>
On Tue, 2017-09-05 at 10:57 +1000, Stephen Rothwell wrote:
> Hi Zhang,
>
> Commits
>
> 1f0d851d9359 ("Debug patch")
> 083d998842a2 ("debug")
>
> are missing a Signed-off-bys.
>
> These are not really appropriate for linux-next inclusion -
> especially
> during the merge window.
>
oops, sorry, wrong branch merged.
thanks,
rui
prev parent reply other threads:[~2017-09-05 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 0:57 linux-next: Signed-off-bys missing for commits in the thermal tree Stephen Rothwell
2017-09-05 1:15 ` Zhang Rui [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=1504574104.3022.1.camel@intel.com \
--to=rui.zhang@intel.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).