public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Henry Zhang <zeri@umich.edu>
Cc: speakup@linux-speakup.org, w.d.hubbs@gmail.com,
	chris@the-brannons.com, kirk@reisers.ca,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] speakup: Document bleeps parameter values
Date: Wed, 28 Jan 2026 10:13:13 +0100	[thread overview]
Message-ID: <aXnTKcilQ5emIvxC@end> (raw)
In-Reply-To: <20260128014501.1600263-1-zeri@umich.edu>

Henry Zhang, le mar. 27 janv. 2026 20:45:01 -0500, a ecrit:
> The speakup documentation had a TODO about accepted values for the
> bleeps parameter. drivers/accessibility/speakup/main.c indicates
> that it's a bitmasked param where bit 0 controls beeping and bit 1
> controls announcements.
> 
> Signed-off-by: Henry Zhang <zeri@umich.edu>

Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

Thanks!

> ---
>  Documentation/ABI/stable/sysfs-driver-speakup | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/ABI/stable/sysfs-driver-speakup b/Documentation/ABI/stable/sysfs-driver-speakup
> index bcb6831aa114..7ead6cb79ca5 100644
> --- a/Documentation/ABI/stable/sysfs-driver-speakup
> +++ b/Documentation/ABI/stable/sysfs-driver-speakup
> @@ -16,8 +16,8 @@ What:		/sys/accessibility/speakup/bleeps
>  KernelVersion:	2.6
>  Contact:	speakup@linux-speakup.org
>  Description:	This controls whether one hears beeps through the PC speaker
> -		when using speakup's review commands.
> -		TODO: what values does it accept?
> +		when using speakup's review commands. Range: 0-3. 0 = off, 1 = beeps
> +		only, 2 = announcements only, 3 = beeps and announcements (default).
>  
>  What:		/sys/accessibility/speakup/bleep_time
>  KernelVersion:	2.6
> -- 
> 2.34.1
> 

      reply	other threads:[~2026-01-28  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28  1:45 [PATCH] speakup: Document bleeps parameter values Henry Zhang
2026-01-28  9:13 ` Samuel Thibault [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=aXnTKcilQ5emIvxC@end \
    --to=samuel.thibault@ens-lyon.org \
    --cc=chris@the-brannons.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@gmail.com \
    --cc=zeri@umich.edu \
    /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