From: Greg KH <gregkh@linuxfoundation.org>
To: niko.mauno@vaisala.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
vesa.jaaskelainen@vaisala.com, geert@linux-m68k.org
Subject: Re: [PATCH v3 1/2] usb: core: Amend initial authorized_default value
Date: Fri, 9 Feb 2024 10:47:01 +0000 [thread overview]
Message-ID: <2024020944-clarinet-nuclear-fe0e@gregkh> (raw)
In-Reply-To: <20240209094651.5379-1-niko.mauno@vaisala.com>
On Fri, Feb 09, 2024 at 11:46:50AM +0200, niko.mauno@vaisala.com wrote:
> From: Niko Mauno <niko.mauno@vaisala.com>
>
> Since the wireless USB implementation has been removed and since the
> behavior with authorized_default values -1 and 1 is now effectively
> same, change the initial value to latter in order to stop using the
> leftover value. The former value can still be passed as a module
> parameter to retain backwards compatibility.
>
> Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
> ---
> drivers/usb/core/hcd.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 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/process/submitting-patches.rst 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
next prev parent reply other threads:[~2024-02-09 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 9:46 [PATCH v3 1/2] usb: core: Amend initial authorized_default value niko.mauno
2024-02-09 9:46 ` [PATCH v3 2/2] usb: core: Make default authorization mode configurable niko.mauno
2024-02-09 10:47 ` Greg KH [this message]
2024-02-09 10:47 ` [PATCH v3 1/2] usb: core: Amend initial authorized_default value Greg KH
2024-02-09 12:39 ` Niko Mauno
2024-02-09 13:34 ` Greg KH
2024-02-09 14:31 ` Niko Mauno
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=2024020944-clarinet-nuclear-fe0e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=niko.mauno@vaisala.com \
--cc=vesa.jaaskelainen@vaisala.com \
/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