From: Greg KH <gregkh@linuxfoundation.org>
To: Shirish Gajera <gajerashirish@gmail.com>
Cc: w.d.hubbs@gmail.com, chris@the-brannons.com, kirk@reisers.ca,
samuel.thibault@ens-lyon.org, domagoj.trsan@gmail.com,
daeseok.youn@gmail.com, roxanagabriela10@gmail.com,
sulamiification@gmail.com, dilekuzulmez@gmail.com,
aysemelikeyurtoglu@gmail.com, ben@decadent.org.uk,
rusty@rustcorp.com.au, tapaswenipathak@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
speakup@linux-speakup.org
Subject: Re: [PATCH Resend] staging: speakup: Fix warning of line over 80 characters.
Date: Sun, 1 Mar 2015 19:40:06 -0800 [thread overview]
Message-ID: <20150302034006.GA29975@kroah.com> (raw)
In-Reply-To: <20150208041901.GA2582@shirish-ThinkPad-Edge-E430>
On Sat, Feb 07, 2015 at 08:19:01PM -0800, Shirish Gajera wrote:
> This patch fixes the checkpatch.pl warning:
>
> WARNING: line over 80 characters
> All line over 80 characters in driver/staging/speakup/* are fixed.
>
> Signed-off-by: Shirish Gajera <gajerashirish@gmail.com>
> ---
> drivers/staging/speakup/main.c | 12 ++++++++----
> drivers/staging/speakup/serialio.h | 3 ++-
> drivers/staging/speakup/speakup.h | 6 ++++--
> drivers/staging/speakup/speakup_decext.c | 6 ++++--
> drivers/staging/speakup/speakup_decpc.c | 6 ++++--
> drivers/staging/speakup/spk_priv.h | 3 ++-
> drivers/staging/speakup/spk_types.h | 3 ++-
> 7 files changed, 26 insertions(+), 13 deletions(-)
This patch fails to apply to my tree. Can you please refresh it against
the staging-testing branch of staging.git and resend?
thanks,
greg k-h
prev parent reply other threads:[~2015-03-02 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 4:19 [PATCH Resend] staging: speakup: Fix warning of line over 80 characters Shirish Gajera
2015-03-02 3:40 ` Greg KH [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=20150302034006.GA29975@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aysemelikeyurtoglu@gmail.com \
--cc=ben@decadent.org.uk \
--cc=chris@the-brannons.com \
--cc=daeseok.youn@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=dilekuzulmez@gmail.com \
--cc=domagoj.trsan@gmail.com \
--cc=gajerashirish@gmail.com \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=roxanagabriela10@gmail.com \
--cc=rusty@rustcorp.com.au \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=sulamiification@gmail.com \
--cc=tapaswenipathak@gmail.com \
--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