All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Chew <achew@nvidia.com>
Cc: linux-kernel@vger.kernel.org, B.Zolnierkiewicz@elka.pw.edu.pl
Subject: Re: [PATCH 2.6.8-rc2] include/linux/ata.h
Date: Wed, 28 Jul 2004 13:15:09 -0400	[thread overview]
Message-ID: <4107DF1D.4070405@pobox.com> (raw)
In-Reply-To: <DCB9B7AA2CAB7F418919D7B59EE45BAF05A1844D@mail-sc-6-bk.nvidia.com>

Andrew Chew wrote:
> The macros ata_id_has_lba() and ata_id_has_dma() seem to have their bits
> reversed.  LBA support is bit 9 of word 49 in the identify page, whereas
> DMA support is bit 8 of word 49 in the identify page.
> 
> 
> --- ata.original.h	2004-07-19 17:49:26.000000000 -0700
> +++ ata.h	2004-07-19 17:49:05.000000000 -0700
> @@ -209,8 +209,8 @@
>  #define ata_id_has_lba48(dev)	((dev)->id[83] & (1 << 10))
>  #define ata_id_has_wcache(dev)	((dev)->id[82] & (1 << 5))
>  #define ata_id_has_pm(dev)	((dev)->id[82] & (1 << 3))
> -#define ata_id_has_lba(dev)	((dev)->id[49] & (1 << 8))
> -#define ata_id_has_dma(dev)	((dev)->id[49] & (1 << 9))
> +#define ata_id_has_lba(dev)	((dev)->id[49] & (1 << 9))
> +#define ata_id_has_dma(dev)	((dev)->id[49] & (1 << 8))
>  #define ata_id_removeable(dev)	((dev)->id[0] & (1 << 7))
>  #define ata_id_u32(dev,n)	\
>  	(((u32) (dev)->id[(n) + 1] << 16) | ((u32) (dev)->id[(n)]))


Patch looks good, but please submit patches generated from the base of 
the kernel tree, so that "patch -sp1 < patch" successfully applies your 
patch.

I am applying this patch manually...

	Jeff



      reply	other threads:[~2004-07-28 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20  1:04 [PATCH 2.6.8-rc2] include/linux/ata.h Andrew Chew
2004-07-28 17:15 ` 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=4107DF1D.4070405@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=achew@nvidia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.