From: Greg KH <gregkh@linuxfoundation.org>
To: Lilis Iskandar <veeableful@gmail.com>
Cc: devel@driverdev.osuosl.org, tulinizer@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Staging: bcm: InterfaceIdleMode: Fixed spacing/tabing issues
Date: Fri, 26 Jul 2013 14:19:51 -0700 [thread overview]
Message-ID: <20130726211951.GA12572@kroah.com> (raw)
In-Reply-To: <1374843573.1802.3.camel@desktop>
On Fri, Jul 26, 2013 at 08:59:33PM +0800, Lilis Iskandar wrote:
> Fixed spacing/tabing issues.
>
> Signed-off-by: Lilis Iskandar <veeableful@gmail.com>
> ---
> drivers/staging/bcm/InterfaceIdleMode.c | 38
> ++++++++++++++++-----------------
> 1 file changed, 19 insertions(+), 19 deletions(-)
All of your patches are line-wrapped, and do not apply :(
Care to fix up your email client and resend them so that I can properly
apply them? This goes for the 6 other patches you sent me as well.
thanks,
greg k-h
next prev parent reply other threads:[~2013-07-26 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 12:59 [PATCH 1/2] Staging: bcm: InterfaceIdleMode: Fixed spacing/tabing issues Lilis Iskandar
2013-07-26 21:19 ` Greg KH [this message]
2013-07-26 21:48 ` Joe Perches
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=20130726211951.GA12572@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tulinizer@gmail.com \
--cc=veeableful@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