linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhinav Saxena <xandfury@gmail.com>
To: linux-sound@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Documentation: sound: Fix trailing whitespaces
Date: Wed, 15 May 2024 04:24:23 +0000	[thread overview]
Message-ID: <ZkQ496Y1SWSr4dDi@server> (raw)
In-Reply-To: <20240515034103.1010269-1-xandfury@gmail.com>

Adding Shuah Khan<skhan@linuxfoundation.org> to cc.

-Abhinav.

On Wed, May 15, 2024 at 03:41:03AM +0000, Abhinav Saxena wrote:
> Remove trailing whitespace from sound/hd-audio/notes as reported by
> checkpatch. Removing trailing spaces improves consistency, and
> prevents Preventing potential merge conflicts due to whitespace
> differences. maintain a cleaner and more professional codebase.
> 
> Signed-off-by: Abhinav Saxena <xandfury@gmail.com>
> ---
>  Documentation/sound/hd-audio/notes.rst | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/Documentation/sound/hd-audio/notes.rst b/Documentation/sound/hd-audio/notes.rst
> index a9e35b1f87bd..ef6a4513cce7 100644
> --- a/Documentation/sound/hd-audio/notes.rst
> +++ b/Documentation/sound/hd-audio/notes.rst
> @@ -15,7 +15,7 @@ problem is broken BIOS, and the rest is the driver implementation.
>  This document explains the brief trouble-shooting and debugging
>  methods for the	HD-audio hardware.
>  
> -The HD-audio component consists of two parts: the controller chip and 
> +The HD-audio component consists of two parts: the controller chip and
>  the codec chips on the HD-audio bus.  Linux provides a single driver
>  for all controllers, snd-hda-intel.  Although the driver name contains
>  a word of a well-known hardware vendor, it's not specific to it but for
> @@ -81,7 +81,7 @@ the wake-up timing.  It wakes up a few samples before actually
>  processing the data on the buffer.  This caused a lot of problems, for
>  example, with ALSA dmix or JACK.  Since 2.6.27 kernel, the driver puts
>  an artificial delay to the wake up timing.  This delay is controlled
> -via ``bdl_pos_adj`` option. 
> +via ``bdl_pos_adj`` option.
>  
>  When ``bdl_pos_adj`` is a negative value (as default), it's assigned to
>  an appropriate value depending on the controller chip.  For Intel
> @@ -144,7 +144,7 @@ see a regression wrt the sound quality (stuttering, etc) or a lock-up
>  in the recent kernel, try to pass ``enable_msi=0`` option to disable
>  MSI.  If it works, you can add the known bad device to the blacklist
>  defined in hda_intel.c.  In such a case, please report and give the
> -patch back to the upstream developer. 
> +patch back to the upstream developer.
>  
>  
>  HD-Audio Codec
> @@ -375,7 +375,7 @@ HD-Audio Reconfiguration
>  ------------------------
>  This is an experimental feature to allow you re-configure the HD-audio
>  codec dynamically without reloading the driver.  The following sysfs
> -files are available under each codec-hwdep device directory (e.g. 
> +files are available under each codec-hwdep device directory (e.g.
>  /sys/class/sound/hwC0D0):
>  
>  vendor_id
> @@ -433,7 +433,7 @@ re-configure based on that state, run like below:
>  ::
>  
>      # echo 0x14 0x9993013f > /sys/class/sound/hwC0D0/user_pin_configs
> -    # echo 1 > /sys/class/sound/hwC0D0/reconfig  
> +    # echo 1 > /sys/class/sound/hwC0D0/reconfig
>  
>  
>  Hint Strings
> @@ -494,7 +494,7 @@ indep_hp (bool)
>      mixer control, if available
>  add_stereo_mix_input (bool)
>      add the stereo mix (analog-loopback mix) to the input mux if
> -    available 
> +    available
>  add_jack_modes (bool)
>      add "xxx Jack Mode" enum controls to each I/O jack for allowing to
>      change the headphone amp and mic bias VREF capabilities
> @@ -504,7 +504,7 @@ power_save_node (bool)
>      stream states
>  power_down_unused (bool)
>      power down the unused widgets, a subset of power_save_node, and
> -    will be dropped in future 
> +    will be dropped in future
>  add_hp_mic (bool)
>      add the headphone to capture source if possible
>  hp_mic_detect (bool)
> @@ -603,7 +603,7 @@ present.
>  
>  The patch module option is specific to each card instance, and you
>  need to give one file name for each instance, separated by commas.
> -For example, if you have two cards, one for an on-board analog and one 
> +For example, if you have two cards, one for an on-board analog and one
>  for an HDMI video board, you may pass patch option like below:
>  ::
>  
> -- 
> 2.34.1
> 

  reply	other threads:[~2024-05-15  4:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  3:41 [PATCH] Documentation: sound: Fix trailing whitespaces Abhinav Saxena
2024-05-15  4:24 ` Abhinav Saxena [this message]
2024-05-16 14:01 ` Takashi Iwai

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=ZkQ496Y1SWSr4dDi@server \
    --to=xandfury@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=skhan@linuxfoundation.org \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).