Hi Linus,
Please pull two patches for 5.4-rc3:
- fix a leftover from earlier stage of development in the documentation
of recently added led_compose_name() and fix old mistake in
the documentation of led_set_brightness_sync() parameter name.
- MAINTAINERS: add pointer to Pavel Machek's linux-leds.git tree.
Pavel is going to take over LED tree maintainership
from myself.
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git tags/led-fixes-for-5.4-rc3
for you to fetch changes up to 4050d21d2009faccae5cab74eeb9f460f25d5108:
Add my linux-leds branch to MAINTAINERS (2019-10-08 22:09:08 +0200)
Thanks,
Jacek Anaszewski
----------------------------------------------------------------
LED fixes for 5.4-rc3.
----------------------------------------------------------------
Dan Murphy (1):
leds: core: Fix leds.h structure documentation
Pavel Machek (1):
Add my linux-leds branch to MAINTAINERS
MAINTAINERS | 1 +
include/linux/leds.h | 5 ++---
2 files changed, 3 insertions(+), 3 deletions(-)
The pull request you sent on Tue, 8 Oct 2019 22:42:58 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git tags/led-fixes-for-5.4-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e3280b54afed870d531571212f1fc375df39b7d2
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker
On Tue 2019-10-08 22:42:58, Jacek Anaszewski wrote:
> Hi Linus,
>
> Please pull two patches for 5.4-rc3:
>
> - fix a leftover from earlier stage of development in the documentation
> of recently added led_compose_name() and fix old mistake in
> the documentation of led_set_brightness_sync() parameter name.
>
> - MAINTAINERS: add pointer to Pavel Machek's linux-leds.git tree.
> Pavel is going to take over LED tree maintainership
> from myself.
Thank you!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Hi!
> - MAINTAINERS: add pointer to Pavel Machek's linux-leds.git tree.
> Pavel is going to take over LED tree maintainership
> from myself.
I pulled latest changes from for-next, so I can take over -next
maintainance for now.
Stephen, could you update your scripts to pull from
git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git ?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Hi Pavel,
On Wed, 9 Oct 2019 14:55:21 +0200 Pavel Machek <[email protected]> wrote:
>
> > - MAINTAINERS: add pointer to Pavel Machek's linux-leds.git tree.
> > Pavel is going to take over LED tree maintainership
> > from myself.
>
> I pulled latest changes from for-next, so I can take over -next
> maintainance for now.
>
> Stephen, could you update your scripts to pull from
> git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git ?
Done.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
[email protected]