From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: arun vijayshankar <arun267@gmail.com>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.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, 03 Dec 2014 17:43:57 -0800 [thread overview]
Message-ID: <1417657437.2902.27.camel@perches.com> (raw)
In-Reply-To: <20141204013925.GA32401@kroah.com>
On Wed, 2014-12-03 at 17:39 -0800, Greg KH wrote:
> On Wed, Dec 03, 2014 at 05:31:59PM -0800, arun vijayshankar wrote:
> > Hi Greg,
>
> If you turn off HTML email, your message will not get rejected by the
> mailing lists :)
>
> > I completely agree! I thought of keeping the patch summary as the subject, but
> > I wasn't sure and ending up entering nothing. Git then used this by default.
>
> You forgot a blank line after your first line in the git commit message,
> which caused it to get all merged together.
>
> Try fixing that up and resending please.
No need. This directory has been deleted.
Please work against -next (or Greg's staging tree)
next prev parent reply other threads:[~2014-12-04 1:44 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
[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 [this message]
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=1417657437.2902.27.camel@perches.com \
--to=joe@perches.com \
--cc=arun267@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox