From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sangho Yi <antiroot@gmail.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Staging: CSR: Fixed 41% of exceeding 80 characters problems on drv.c
Date: Thu, 18 Oct 2012 16:36:38 +0300 [thread overview]
Message-ID: <20121018133638.GP5685@mwanda> (raw)
In-Reply-To: <1350230306-32515-2-git-send-email-antiroot@gmail.com>
On Mon, Oct 15, 2012 at 12:58:26AM +0900, Sangho Yi wrote:
> -int buswidth = 0; /* 0 means use default, values 1,4 */
> -int sdio_clock = 50000; /* kHz */
> +int buswidth = 0; /* 0 means use default, values 1,4 */
> +int sdio_clock = 50000; /* kHz */
These are nonsense indenting. :(
regards,
dan carpenter
next prev parent reply other threads:[~2012-10-18 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 15:58 [PATCH 1/2] Staging: CSR: Fixed indentation problems on drv.c (tab mess) Sangho Yi
2012-10-14 15:58 ` [PATCH 2/2] Staging: CSR: Fixed 41% of exceeding 80 characters problems on drv.c Sangho Yi
2012-10-18 13:36 ` Dan Carpenter [this message]
2012-10-22 21:03 ` Greg KH
2012-10-18 13:34 ` [PATCH 1/2] Staging: CSR: Fixed indentation problems on drv.c (tab mess) Dan Carpenter
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=20121018133638.GP5685@mwanda \
--to=dan.carpenter@oracle.com \
--cc=antiroot@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