From: Greg KH <gregkh@linuxfoundation.org>
To: shirish gajera <gajerashirish@gmail.com>
Cc: "William Hubbs" <w.d.hubbs@gmail.com>,
"Christopher Brannon" <chris@the-brannons.com>,
kirk@reisers.ca, "Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Domagoj Tršan" <domagoj.trsan@gmail.com>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
"Ben Hutchings" <ben@decadent.org.uk>,
"Roxana Blaj" <roxanagabriela10@gmail.com>,
"Robin Schroer" <sulamiification@gmail.com>,
"Dilek Üzülmez" <dilekuzulmez@gmail.com>,
"DaeSeok Youn" <daeseok.youn@gmail.com>,
"Ayşe Melike Yurtoğlu" <aysemelikeyurtoglu@gmail.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
tapaswenipathak@gmail.com, sasha.levin@oracle.com,
speakup@linux-speakup.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: speakup: Fix warning of line over 80 characters.
Date: Sun, 8 Feb 2015 08:33:25 +0800 [thread overview]
Message-ID: <20150208003325.GC2504@kroah.com> (raw)
In-Reply-To: <CAG77vrqfrAdQErz91Nq+7j_mjBigSkL9EGuejdyOo8553p2hBA@mail.gmail.com>
On Sat, Feb 07, 2015 at 09:46:37AM -0800, shirish gajera wrote:
> On Sat, Feb 7, 2015 at 1:09 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Sat, Jan 31, 2015 at 02:19:43PM -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.
> > Aditional changes suggest by mailing list are also 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 ++-
> > drivers/staging/speakup/synth.c | 10 +++++-----
> > 8 files changed, 31 insertions(+), 18 deletions(-)
>
> This fails to apply to my tree for some reason :(
>
> Can you refresh it and resend?
>
> thanks,
>
> greg k-h
>
>
>
> It is already refreshed from last time.
>
> Can you clarify refresh means git pull and resend right ? Is there any other
> way of refresh ?
Yes it does. What tree and branch are you making these against? They
should be against my staging.git tree on git.kernel.org, and against the
staging-testing branch. Anything else might have conflicts.
thanks,
greg k-h
next prev parent reply other threads:[~2015-02-08 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 22:19 [PATCH v2] staging: speakup: Fix warning of line over 80 characters Shirish Gajera
2015-02-07 9:09 ` Greg KH
[not found] ` <CAG77vrqfrAdQErz91Nq+7j_mjBigSkL9EGuejdyOo8553p2hBA@mail.gmail.com>
2015-02-08 0:33 ` Greg KH [this message]
[not found] ` <CAG77vrpd7Fy2bKCEKJ_Z=j6fJfsKLANkWf6KB1ErjPLQm4b-0g@mail.gmail.com>
2015-02-08 2:43 ` Greg KH
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=20150208003325.GC2504@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=dan.carpenter@oracle.com \
--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=sasha.levin@oracle.com \
--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