From: Greg KH <gregkh@linuxfoundation.org>
To: Ramesh Basukala <basukalaramesh@gmail.com>
Cc: lisa@xenapiadmin.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: bmc: fix coding style warning
Date: Fri, 15 Aug 2014 14:55:06 +0800 [thread overview]
Message-ID: <20140815065506.GA26102@kroah.com> (raw)
In-Reply-To: <1408025504-19100-1-git-send-email-basukalaramesh@gmail.com>
On Thu, Aug 14, 2014 at 10:11:44AM -0400, Ramesh Basukala wrote:
> This is a patch to the vendorspecificextn.c that fixes coding style
> warning message line over 80 characters found by checkpatch.pl script.
> I am submitting this patch as required by Eudyptula Challenge.
Minor nit, your subject is wrong, the driver is 'bcm' not 'bmc' :)
next prev parent reply other threads:[~2014-08-15 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 15:36 [PATCH] Staging: bmc: fix coding style warning rbasukala
2014-08-13 22:06 ` Greg KH
2014-08-14 0:53 ` Ramesh Basukala
2014-08-14 1:20 ` Greg KH
2014-08-14 14:11 ` Ramesh Basukala
2014-08-15 6:55 ` Greg KH [this message]
2014-08-15 15:50 ` [PATCH] Staging: bcm: " Ramesh Basukala
2014-08-17 16:50 ` 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=20140815065506.GA26102@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=basukalaramesh@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@xenapiadmin.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