From: Matthias Brugger <matthias.bgg@gmail.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>,
Sean Wang <sean.wang@mediatek.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the mediatek tree
Date: Mon, 14 May 2018 12:47:48 +0200 [thread overview]
Message-ID: <01b4e66c-8c1d-1ea7-d35e-3555a3c3eeb0@gmail.com> (raw)
In-Reply-To: <20180514075745.168494a9@canb.auug.org.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Stephen,
On 05/13/2018 11:57 PM, Stephen Rothwell wrote:
> Hi Matthias,
>
> Commit
>
> f039c4193c93 ("iregmap: include <linux/ktime.h> from
> include/linux/regmap.h")
>
> is missing a Signed-off-by from its committer.
>
My tree was broken and the merge commit disappeared which pulled this commit
into my tree. Should be fixed by now.
Regards,
Matthias
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEiUuSfQSYnG8EMsBltDliWyzx00MFAlr5aU0ACgkQtDliWyzx
00O68Q//eXk6z6PiRXG+30Pk5z5Wl3vmEvEokwivO1I1kCErktyAcvjMNYA5CJS+
Df7FWAg3p17G7e6p7w5NOteOxBI4leCsebLnRMKOja2m6IrulxHb98koAjcx14sx
twKsa2YEMI7GjhwE93ozkoqkeGeQ0i/IxyFRqn0brcpmUv/49AY8Qw4VTi/Q5rxm
ma6YFWygcQ7x603eWrkxJKG5pmExmUTwNU7B+9Ycqp/yMaikUYW9RedToDxjILAJ
OGQ2uexySNyUJaX2ECpHeM7FnSkOBKzqAjzCD8bDQTL82hiUla5mDFRsOhtzg9be
pe/CdChbeLxZ0v8fv1n2WEO4Bb1E6OXp7YmL8hH6nbmWVxQf448QX0POV5IrJX+V
46/iMzwUtjTasAj50RoI8cb3mhj0fcJgmB/Ivk6OZQfy1UoZ0VrPjIiNlymfgTGM
aP28Dx8RUxysZCvj0Uy/CX+kxMxJU77OgOMDxotf8iTAVnbC2dSqiHSkqZCj7ncK
1cVQkfUHvqEgtCdsEyHN+k7fcu2vmYwvISE5IpoKZyHPU1CNc5+cFdEbxlCvUVVJ
K9PNYz8VFJsYJyYcVG+1C4EUJHLRrnhTK6cdp5GaKlSHagV8UKaefuUvXU8GRBZm
BO+xTm6qRX5ZnQI57MPaq/xEvhVevMRG4xp0wZ5Bf86uIvlP97w=
=gxCq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-05-14 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 21:57 linux-next: Signed-off-by missing for commit in the mediatek tree Stephen Rothwell
2018-05-14 10:47 ` Matthias Brugger [this message]
2022-04-25 22:07 Stephen Rothwell
2022-04-26 8:48 ` Matthias Brugger
2022-04-26 8:52 ` Krzysztof Kozlowski
2022-04-26 8:53 ` Krzysztof Kozlowski
2022-04-26 8:55 ` Matthias Brugger
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=01b4e66c-8c1d-1ea7-d35e-3555a3c3eeb0@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).