linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] ata_piix: CodingStyle fixes
Date: Fri, 14 Oct 2011 13:36:16 -0400	[thread overview]
Message-ID: <4E987310.1050401@pobox.com> (raw)
In-Reply-To: <201110131543.30235.bzolnier@gmail.com>

On 10/13/2011 09:43 AM, Bartlomiej Zolnierkiewicz wrote:
> From: Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>
> Subject: [PATCH] ata_piix: CodingStyle fixes
>
> CodingStyle fixes for piix_port_info[].
>
> Signed-off-by: Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>
> ---
>   drivers/ata/ata_piix.c |   68 ++++++++++++++-----------------------------------
>   1 file changed, 20 insertions(+), 48 deletions(-)
>
> Index: b/drivers/ata/ata_piix.c
> ===================================================================
> --- a/drivers/ata/ata_piix.c
> +++ b/drivers/ata/ata_piix.c
> @@ -473,131 +473,103 @@ static const struct piix_map_db *piix_ma
>   };
>
>   static struct ata_port_info piix_port_info[] = {
> -	[piix_pata_mwdma] = 	/* PIIX3 MWDMA only */
> -	{
> +	[piix_pata_mwdma] = {	/* PIIX3 MWDMA only */
>   		.flags		= PIIX_PATA_FLAGS,
>   		.pio_mask	= ATA_PIO4,
> -		.mwdma_mask	= ATA_MWDMA12_ONLY, /* mwdma1-2 ?? CHECK 0 should be ok but slow */
> +		.mwdma_mask	= ATA_MWDMA12_ONLY, /* check if MWDMA0 is OK */
>   		.port_ops	=&piix_pata_ops,
>   	},

Having been the perpetrator of this "awful" coding style, I think it is 
fine and more readable as-is...  :)



      reply	other threads:[~2011-10-14 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 13:43 [PATCH v2 3/4] ata_piix: CodingStyle fixes Bartlomiej Zolnierkiewicz
2011-10-14 17:36 ` Jeff Garzik [this message]

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=4E987310.1050401@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).