From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the iio tree
Date: Tue, 8 Aug 2023 09:26:08 +0300 [thread overview]
Message-ID: <f7a20a95-48fa-edc0-9724-bfb4484c155a@gmail.com> (raw)
In-Reply-To: <20230808083925.7109a675@canb.auug.org.au>
Thanks Stephen!
On 8/8/23 01:39, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> a00cf70f16c9 ("iio: light: bd27008: Support BD27010 RGB")
> 16a9947646f7 ("iio: light: bu27008: add chip info")
> ae8c47c51e5c ("dt-bindings: iio: ROHM BU27010 RGBC + flickering sensor")
>
> are missing a Signed-off-by from their committer.
>
I am 99% sure I had SoB tags added in patches. Seems like they have been
lost in the action.
Jonathan, do you need me to respin patches or how do you think we should
fix this?
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2023-08-08 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 22:39 linux-next: Signed-off-by missing for commit in the iio tree Stephen Rothwell
2023-08-08 6:26 ` Matti Vaittinen [this message]
2023-08-08 6:29 ` Matti Vaittinen
2023-08-08 7:56 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2023-09-11 23:05 Stephen Rothwell
2023-09-12 6:37 ` Hennerich, Michael
2023-09-12 9:20 ` Jonathan Cameron
2023-09-12 11:27 ` Hennerich, Michael
2025-05-04 21:48 Stephen Rothwell
2025-05-05 15:43 ` David Lechner
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=f7a20a95-48fa-edc0-9724-bfb4484c155a@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=Jonathan.Cameron@Huawei.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