Messages in this thread | | | Date | Sat, 22 Jan 2022 08:32:25 +0100 | From | Greg Kroah-Hartman <> | Subject | Re: [PATCH 22/31] tty: vt: changing LED_* from enum led_brightness to actual value |
| |
On Fri, Jan 21, 2022 at 01:54:27PM -0300, Luiz Sampaio wrote: > The enum led_brightness, which contains the declaration of LED_OFF, > LED_ON, LED_HALF and LED_FULL is obsolete, as the led class now supports > max_brightness. > --- > drivers/tty/vt/keyboard.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/tty/vt/keyboard.c b/drivers/tty/vt/keyboard.c > index be8313cdbac3..33bad1973180 100644 > --- a/drivers/tty/vt/keyboard.c > +++ b/drivers/tty/vt/keyboard.c > @@ -1035,7 +1035,7 @@ static int kbd_led_trigger_activate(struct led_classdev *cdev) > if (ledstate != -1U) > led_trigger_event(&trigger->trigger, > ledstate & trigger->mask ? > - LED_FULL : LED_OFF); > + 255 : 0); > tasklet_enable(&keyboard_tasklet); > > return 0; > @@ -1081,7 +1081,7 @@ static void kbd_propagate_led_state(unsigned int old_state, > if (changed & trigger->mask) > led_trigger_event(&trigger->trigger, > new_state & trigger->mask ? > - LED_FULL : LED_OFF); > + 255 : 0); > } > } > > -- > 2.34.1 >
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.
You are receiving this message because of the following common error(s) as indicated below:
- Your patch does not have a Signed-off-by: line. Please read the kernel file, Documentation/SubmittingPatches and resend it after adding that line. Note, the line needs to be in the body of the email, before the patch, not at the bottom of the patch or in the email signature.
If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.
thanks,
greg k-h's patch email bot
| |