From: Pavel Machek <pavel@ucw•cz>
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>
Subject: Re: linux-next: Signed-off-by missing for commits in the leds tree
Date: Sun, 20 Sep 2020 23:37:25 +0200 [thread overview]
Message-ID: <20200920213725.GA31397@duo.ucw.cz> (raw)
In-Reply-To: <20200921061638.28bb1ff3@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Hi!
> 258a8388d0ec ("leds: ns2: use struct led_init_data when registering")
> d444232bbbdd ("leds: ns2: remove unneeded variable")
> 29c44f2b51a8 ("leds: ns2: register LED immediately after parsing DT properties")
> 925533c5a040 ("leds: ns2: cosmetic change: use helper variable")
> 47f1fb852be2 ("leds: ns2: cosmetic change")
> a2ca4110ffc9 ("leds: ns2: cosmetic variable rename")
> 2d55e2a22ef0 ("leds: ns2: cosmetic structure rename")
> 51822355a756 ("leds: ns2: use devres API for getting GPIO descriptors")
> e6367d0d57cb ("leds: ns2: move parsing of one LED into separate function")
> a5c8eb177993 ("leds: ns2: support OF probing only, forget platdata")
> 820a7e98dbc3 ("leds: ns2: alloc simple array instead of struct ns2_led_priv")
> 5943b5ceb7f2 ("leds: ns2: use devres LED registering function")
>
> are missing a Signed-off-by from their committer.
Thanks for heads-up. Fixed and force-pushed.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-09-20 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 20:16 linux-next: Signed-off-by missing for commits in the leds tree Stephen Rothwell
2020-09-20 21:37 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-15 21:15 Stephen Rothwell
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=20200920213725.GA31397@duo.ucw.cz \
--to=pavel@ucw$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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