mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <edubezval@gmail.com>
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-by missing for commit in the thermal tree
Date: Sat, 21 Mar 2020 10:04:52 +0100	[thread overview]
Message-ID: <4743bfd4-f771-8a0d-56e7-2e9c36bb557a@linaro.org> (raw)
In-Reply-To: <20200321161556.212a9fa1@canb.auug.org.au>

On 21/03/2020 06:15, Stephen Rothwell wrote:
> Hi all,
> 
> Commits
> 
>   791f2cfb145d ("tools/thermal: tmon: replace error message SIGINT with SIGTERM")
>   65ae2fb88af1 ("thermal: int340x: processor_thermal: Add Tiger Lake support")
>   1bfd0bd3f6e0 ("thermal: intel_pch_thermal: Add PCI ids for Lewisburg PCH.")
>   c17ea0c7f386 ("thermal: stm32: make stm_thermal_pm_ops static")
>   45921a2ac8a5 ("thermal/x86_pkg_temp: Make pkg_temp_lock a raw_spinlock_t")
> 
> are missing a Signed-off-by from their committers.

Fixed, thanks


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2020-03-21  9:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21  5:15 Stephen Rothwell
2020-03-21  9:04 ` Daniel Lezcano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-12 21:48 Stephen Rothwell
2022-12-13  9:09 ` Daniel Lezcano
2021-04-22 21:46 Stephen Rothwell
2020-07-18  8:35 Stephen Rothwell
2019-12-06 23:55 Stephen Rothwell
2019-12-07 13:59 ` Zhang Rui

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=4743bfd4-f771-8a0d-56e7-2e9c36bb557a@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --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

all inboxes | Powered by JetHome®