From: Greg KH <gregkh@linuxfoundation.org>
To: Arun <arun267@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: bcm: Fix lines exceeding 80 character limit in CmHost.h This is a patch to CmHost.h that fixes Exceeds 80 Character limits warning found by checkpatch.pl Signed-off-by: Arun Ayyer <arun267@gmail.com>
Date: Wed, 3 Dec 2014 17:25:17 -0800 [thread overview]
Message-ID: <20141204012517.GA31563@kroah.com> (raw)
In-Reply-To: <1417655529-8640-1-git-send-email-arun267@gmail.com>
On Wed, Dec 03, 2014 at 05:12:09PM -0800, Arun wrote:
> ---
> drivers/staging/bcm/CmHost.h | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
That's a really odd subject, don't you agree?
:)
next prev parent reply other threads:[~2014-12-04 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 1:12 [PATCH] Staging: bcm: Fix lines exceeding 80 character limit in CmHost.h This is a patch to CmHost.h that fixes Exceeds 80 Character limits warning found by checkpatch.pl Signed-off-by: Arun Ayyer <arun267@gmail.com> Arun
2014-12-04 1:25 ` Greg KH [this message]
[not found] ` <CAJ8d=beEFz-wKaN4bodZFN9BCrUsZKy=F0e-R7fUVXsf+04g4A@mail.gmail.com>
2014-12-04 1:39 ` Greg KH
2014-12-04 1:43 ` Joe Perches
2014-12-04 1:53 ` arun vijayshankar
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=20141204012517.GA31563@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arun267@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.