From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Hsin-Te Yuan <yuanhsinte@chromium.org>,
Daolong Zhu <jg_daolongzhu@mediatek.corp-partner.google.com>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Chen-Yu Tsai <wenst@chromium.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the mediatek tree
Date: Wed, 9 Oct 2024 16:53:33 -0400 [thread overview]
Message-ID: <20241009-prudent-pompous-sheep-40ed20@lemur> (raw)
In-Reply-To: <c97da0be-6924-48de-9cf3-0ba9d5e6a73e@kernel.org>
On Wed, Oct 09, 2024 at 09:52:14AM GMT, AngeloGioacchino Del Regno wrote:
> > 65b99309a9c1 ("arm64: dts: mt8183: Damu: add i2c2's i2c-scl-internal-delay-ns")
> > 025869564bf8 ("arm64: dts: mt8183: cozmo: add i2c2's i2c-scl-internal-delay-ns")
> > 3d3bc7cb46e8 ("arm64: dts: mt8183: burnet: add i2c2's i2c-scl-internal-delay-ns")
> > 5bbddfd0470f ("arm64: dts: mt8183: fennel: add i2c2's i2c-scl-internal-delay-ns")
> > (The above also has an empty Reviewed-by tag)
> > ca80f75083f6 ("arm64: dts: mt8183: set DMIC one-wire mode on Damu")
> >
> > are missing a Signed-off-by from their authors.
> >
>
> The empty R-b happened because b4 didn't interpret "<email>2" correctly
> and dropped the email entirely. We should probably report that to the authors.
Consider it reported. :) However, I'm not sure I understand what the situation
is. When I pull that series with ``b4 -slH shazam``, all the trailers are
properly preserved as far as I can tell:
arm64: dts: mt8183: Damu: add i2c2's i2c-scl-internal-delay-ns
Add i2c2's i2c-scl-internal-delay-ns.
Fixes: cabc71b08eb5 ("arm64: dts: mt8183: Add kukui-jacuzzi-damu board")
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Daolong Zhu <jg_daolongzhu@mediatek.corp-partner.google.com>
Signed-off-by: Hsin-Te Yuan <yuanhsinte@chromium.org>
Link: https://lore.kernel.org/r/20241009-i2c-delay-v1-4-6cf59721c1d1@chromium.org
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
-K
next prev parent reply other threads:[~2024-10-09 20:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 20:15 linux-next: Signed-off-by missing for commit in the mediatek tree Stephen Rothwell
2024-10-09 7:52 ` AngeloGioacchino Del Regno
[not found] ` <CAHc4DNKx1WLK-QnxTo-f1djCzhRq0MPqD=Z7szHw7+eZAjU1_g@mail.gmail.com>
2024-10-09 8:39 ` AngeloGioacchino Del Regno
2024-10-09 20:53 ` Konstantin Ryabitsev [this message]
2024-10-10 9:21 ` AngeloGioacchino Del Regno
-- strict thread matches above, loose matches on Subject: below --
2025-02-24 22:17 Stephen Rothwell
2025-02-25 8:57 ` AngeloGioacchino Del Regno
2024-10-09 21:03 Stephen Rothwell
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
2018-05-13 21:57 Stephen Rothwell
2018-05-14 10:47 ` 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=20241009-prudent-pompous-sheep-40ed20@lemur \
--to=konstantin@linuxfoundation.org \
--cc=angelogioacchino.delregno@kernel.org \
--cc=hsinyi@chromium.org \
--cc=jg_daolongzhu@mediatek.corp-partner.google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=wenst@chromium.org \
--cc=yuanhsinte@chromium.org \
/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