The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Marek Belisko <marek.belisko@open-nandra.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend 07/12] staging: ft1000: Fix coding style in get_request_type() function.
Date: Tue, 25 Jan 2011 15:23:43 +0300	[thread overview]
Message-ID: <20110125122343.GE2721@bicker> (raw)
In-Reply-To: <1295955083-11086-7-git-send-email-marek.belisko@open-nandra.com>

On Tue, Jan 25, 2011 at 12:31:18PM +0100, Marek Belisko wrote:
>  static u16 get_request_type(struct ft1000_device *ft1000dev)
>  {
> -   u16   request_type;
> -   u32    status;
> -   u16   tempword;
> -   u32    tempx;
> +	u16   request_type;
> +	u32    status;
> +	u16   tempword;
> +	u32    tempx;
              ^^
The alignment is sort of whacky looking.

regards,
dan carpenter



  reply	other threads:[~2011-01-25 12:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 11:31 [PATCH resend 01/12] staging: ft1000: Use common return point Marek Belisko
2011-01-25 11:31 ` [PATCH resend 02/12] staging: ft1000: Remove dead code Marek Belisko
2011-01-25 11:31 ` [PATCH resend 03/12] staging: ft1000: Fix coding style in check_usb_db() function Marek Belisko
2011-01-25 11:31 ` [PATCH resend 04/12] staging: ft1000: Fix coding style in put_handshake() function Marek Belisko
2011-01-25 11:31 ` [PATCH resend 05/12] staging: ft1000: Fix coding style in get_handshake_usb() function Marek Belisko
2011-01-25 12:14   ` Dan Carpenter
2011-01-25 11:31 ` [PATCH resend 06/12] staging: ft1000: Fix coding style in put_handshake_usb() function Marek Belisko
2011-01-25 11:31 ` [PATCH resend 07/12] staging: ft1000: Fix coding style in get_request_type() function Marek Belisko
2011-01-25 12:23   ` Dan Carpenter [this message]
2011-01-25 11:31 ` [PATCH resend 08/12] staging: ft1000: Fix coding style in get_request_type_usb() function Marek Belisko
2011-01-25 12:25   ` Dan Carpenter
2011-01-25 11:31 ` [PATCH resend 09/12] staging: ft1000: Fix coding style in get_request_value() function Marek Belisko
2011-01-25 12:28   ` Dan Carpenter
2011-01-25 11:31 ` [PATCH resend 10/12] staging: ft1000: Fix coding style in put_request_value() function Marek Belisko
2011-01-25 11:31 ` [PATCH resend 11/12] staging: ft1000: Fix coding style in hdr_checksum() function Marek Belisko
2011-01-25 11:31 ` [PATCH resend 12/12] staging: ft1000: Fix coding style in get_handshake() function Marek Belisko
2011-01-25 12:04 ` [PATCH resend 01/12] staging: ft1000: Use common return point 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=20110125122343.GE2721@bicker \
    --to=error27@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.belisko@open-nandra.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