mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niko Mauno <niko.mauno@vaisala.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, vesa.jaaskelainen@vaisala.com
Subject: Re: [PATCH v2 2/2] usb: core: Make default authorization mode configurable
Date: Fri, 9 Feb 2024 11:55:40 +0200	[thread overview]
Message-ID: <3fdd409f-25de-4a5e-875a-8b59a1a0c0cc@vaisala.com> (raw)
In-Reply-To: <CAMuHMdUy793gzDVR0jfNnx5TUdJ_2MKH5NPGSgHkytAhArtqmw@mail.gmail.com>

On 6.2.2024 16.33, Geert Uytterhoeven wrote:
> On Fri, Jan 5, 2024 at 12:51 PM <niko.mauno@vaisala.com> wrote:
...
>> +         The available values have the following meanings:
>> +               0 is unauthorized for all devices
>> +               1 is authorized for all devices (default)
>> +               2 is authorized for internal devices
>> +
>> +         If the default value is too permissive but you are unsure which mode
>> +         to use, say 2.
> 
> I'm sorry, but I don't have any clue about what to answer to this question.
> Usually, you are (or are not) authorized to do _something_, but the
> /something/ is not mentioned at all here.
> Can you please make this a bit more clear?
> Thanks!

Thanks, submitted v3 which is hopefully better in this respect.
-Niko

      reply	other threads:[~2024-02-09  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 11:49 [PATCH v2 1/2] usb: core: Amend initial authorized_default value niko.mauno
2024-01-05 11:49 ` [PATCH v2 2/2] usb: core: Make default authorization mode configurable niko.mauno
2024-02-06 14:33   ` Geert Uytterhoeven
2024-02-09  9:55     ` Niko Mauno [this message]

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=3fdd409f-25de-4a5e-875a-8b59a1a0c0cc@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®