mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niko Mauno <niko.mauno@vaisala.com>
To: Greg KH <gregkh@linuxfoundation.org>
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 14:39:01 +0200	[thread overview]
Message-ID: <65582610-72ba-4644-9032-91c09f50a6bf@vaisala.com> (raw)
In-Reply-To: <2024020903-october-placidly-20cc@gregkh>

On 9.2.2024 12.47, Greg KH wrote:
> 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(-)
> 
> Isn't this series already in my tree?
> 
> confused,
> 
> greg k-h

Hi Greg, apologies for any confusion I may have caused,

Geert requested some further clarification in the new Kconfig help 
section, please see:
https://marc.info/?l=linux-usb&m=170747246528305&w=2

(There shouldn't be any functional change introduced between v2 and v3)

Kind regards,
-Niko

  reply	other threads:[~2024-02-09 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09  9:46 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 ` [PATCH v3 1/2] usb: core: Amend initial authorized_default value Greg KH
2024-02-09 10:47 ` Greg KH
2024-02-09 12:39   ` Niko Mauno [this message]
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=65582610-72ba-4644-9032-91c09f50a6bf@vaisala.com \
    --to=niko.mauno@vaisala.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®