public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "Panir.Nyan" <panir.nyan@gmail.com>
Cc: gregkh@linuxfoundation.org, w.d.hubbs@gmail.com,
	chris@the-brannons.com, kirk@reisers.ca,
	speakup@linux-speakup.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: speakup: Split the comment to fit the length
Date: Wed, 24 Dec 2014 16:41:57 +0100	[thread overview]
Message-ID: <20141224154157.GS3060@type> (raw)
In-Reply-To: <1419394052-6551-1-git-send-email-Panir.Nyan@gmail.com>

Panir.Nyan, le Wed 24 Dec 2014 04:07:31 +0000, a écrit :
> Split the comment to fit the length.
> 
> Signed-off-by: Panir Nyan <Panir.Nyan@gmail.com>

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

> ---
>  drivers/staging/speakup/synth.c |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c
> index f3aa423..01eddab 100644
> --- a/drivers/staging/speakup/synth.c
> +++ b/drivers/staging/speakup/synth.c
> @@ -30,9 +30,9 @@ struct speakup_info_t speakup_info = {
>  	 * must be taken at each kernel->speakup transition and released at
>  	 * each corresponding speakup->kernel transition.
>  	 *
> -	 * The progression thread only interferes with the speakup machinery through
> -	 * the synth buffer, so only needs to take the lock while tinkering with
> -	 * the buffer.
> +	 * The progression thread only interferes with the speakup machinery
> +	 * through the synth buffer, so only needs to take the lock
> +	 * while tinkering with the buffer.
>  	 *
>  	 * We use spin_lock/trylock_irqsave and spin_unlock_irqrestore with this
>  	 * spinlock because speakup needs to disable the keyboard IRQ.
> --
> 1.7.10.4
> 

-- 
Samuel
Linux, c'est simple : ça s'adresse à une machine qui est parfois un peu
maraboutée mais qui d'habitude n'a pas d'états d'âme. Sur Usenet y'a
plein d'humains et de primates, et ça devient vraiment gore par moment.
-+- TP in : Guide du linuxien pervers - "Le linuxien a-t-il une âme ?" -+-

      parent reply	other threads:[~2014-12-24 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  4:07 [PATCH 1/2] staging: speakup: Split the comment to fit the length Panir.Nyan
2014-12-24  4:07 ` [PATCH 2/2] staging: speakup: Combine the consecutive string Panir.Nyan
2014-12-24 15:44   ` Samuel Thibault
2014-12-24 15:41 ` 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=20141224154157.GS3060@type \
    --to=samuel.thibault@ens-lyon.org \
    --cc=chris@the-brannons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=panir.nyan@gmail.com \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@gmail.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