On Wed, Sep 28, 2022 at 06:30:05PM +0530, Rajat Khandelwal wrote: > Wake on connect/disconnect is only supported while runtime suspend > for now, which is obviously necessary. Its also not inherently > desired for the system to wakeup on thunderbolt hot events. > However, we can still make user in control of waking up the system > in the events of hot plug/unplug. > This patch adds 'wakeup' attribute under 'usb4_portX/power' sysfs > attribute and only enables wakes on connect/disconnect to the > respective port when 'wakeup' is set to 'enabled'. The attribute > is set to 'disabled' by default. > > Signed-off-by: Rajat Khandelwal <rajat.khandelwal@xxxxxxxxx> Including the issue pointed out below by my bot, Intel has a "special" requirement that you are not meeting here in order to send out patches for review on a public mailing list in a subsystem like this (i.e. one that I and others review patches on.) Please meet that requirement first before sending any future kernel patches out. > --- > > drivers/thunderbolt/tb_regs.h | 2 ++ > drivers/thunderbolt/usb4.c | 33 +++++++++++++++++++++++++-------- > drivers/thunderbolt/usb4_port.c | 3 +++ > 3 files changed, 30 insertions(+), 8 deletions(-) > 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: - This looks like a new version of a previously submitted patch, but you did not list below the --- line any changes from the previous version. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what needs to be done here to properly describe this. 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
