From: Benson Leung <bleung@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Guenter Roeck <groeck@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gwendal Grignou <gwendal@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
bleung@google.com
Subject: Re: linux-next: Signed-off-by missing for commits in the chrome-platform tree
Date: Mon, 17 Jun 2019 14:49:27 -0700 [thread overview]
Message-ID: <20190617214927.GA68491@google.com> (raw)
In-Reply-To: <20190618074607.09dfcdbd@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2349 bytes --]
Hi Stephen,
On Tue, Jun 18, 2019 at 07:46:07AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 0ac39915c00e ("mfd: cros_ec: Update I2S API")
> 273e4a83784f ("mfd: cros_ec: Add Management API entry points")
> 5fb684b28ddf ("mfd: cros_ec: Add SKU ID and Secure storage API")
> fa1edb8224c9 ("mfd: cros_ec: Add API for rwsig")
> a5a60125c987 ("mfd: cros_ec: Add API for Fingerprint support")
> ff5599529a19 ("mfd: cros_ec: Add API for Touchpad support")
> a97c5892c8cf ("mfd: cros_ec: Add API for EC-EC communication")
> 381041521d3a ("mfd: cros_ec: Add I2C passthru protection API")
> d18e0cde8705 ("mfd: cros_ec: Add Smart Battery Firmware update API")
> e4de049a3892 ("mfd: cros_ec: Add Hibernate API")
> 44f251dc6e69 ("mfd: cros_ec: Add API for keyboard testing")
> 03dc9f7cdc8a ("mfd: cros_ec: Complete Power and USB PD API")
> a704e1450f07 ("mfd: cros_ec: Fix temperature API")
> fa5a714e9d54 ("mfd: cros_ec: Add fingerprint API")
> cbc1d3b7c5a4 ("mfd: cros_ec: Fix event processing API")
> b841c3496d0d ("mfd: cros_ec: Complete MEMS sensor API")
> b4e686e9eecd ("mfd: cros_ec: Add EC transport protocol v4")
> 743875b6af81 ("mfd: cros_ec: Expand hash API")
> 051cf1f83491 ("mfd: cros_ec: Add lightbar v2 API")
> b1bd73c9e90f ("mfd: cros_ec: Add PWM_SET_DUTY API")
> 998b37cad349 ("mfd: cros_ec: Add Flash V2 commands API")
> d8064663d3c4 ("mfd: cros_ec: Remove zero-size structs")
> 036957c19978 ("mfd: cros_ec: move HDMI CEC API definition")
> 0ee2b17ec310 ("mfd: cros_ec: Update ACPI interface definition")
> 6f6db199e544 ("mfd: cros_ec: use BIT macro")
> a5f0ac50978b ("mfd: cros_ec: Define commands as 4-digit UPPER CASE hex values")
> de18e8beadcc ("mfd: cros_ec: add ec_align macros")
> bf96c5f1276c ("mfd: cros_ec: set comments properly")
> 6b854d5fbda9 ("mfd: cros_ec: Zero BUILD_ macro")
> 5a0d32c91830 ("mfd: cros_ec: Update license term")
>
> are missing a Signed-off-by from their committer.
>
> These were all rebased.
>
Yup, Enric and I caught this this morning. You're right, this was an inadvertent
rebase. We'll fix the for-next branch for tomorrow.
Thanks,
Benson
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2019-06-17 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 21:46 linux-next: Signed-off-by missing for commits in the chrome-platform tree Stephen Rothwell
2019-06-17 21:49 ` Benson Leung [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=20190617214927.GA68491@google.com \
--to=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=lee.jones@linaro.org \
--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).