linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/2] libata: add CFA specific identify data words
Date: Mon, 13 Apr 2009 13:16:53 -0400	[thread overview]
Message-ID: <49E37385.6070506@pobox.com> (raw)
In-Reply-To: <49E36F3F.6080907@ru.mvista.com>

Sergei Shtylyov wrote:
> Jeff Garzik wrote:
> 
>>>>>> Declare and use constants for CFA specific identify data words 162 
>>>>>> and 163.
> 
>>>>>> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> 
>>>>>    Jeff, have you forgotten about this one too?
> 
>>>>>> Index: linux-2.6/drivers/ata/libata-core.c
>>>>>> ===================================================================
>>>>>> --- linux-2.6.orig/drivers/ata/libata-core.c
>>>>>> +++ linux-2.6/drivers/ata/libata-core.c
>>>>>> @@ -1650,8 +1650,8 @@ unsigned long ata_id_xfermask(const 
>>>>>> u16          /*
>>>>>>           *    Process compact flash extended modes
>>>>>>           */
>>>>>> -        int pio = id[163] & 0x7;
>>>>>> -        int dma = (id[163] >> 3) & 7;
>>>>>> +        int pio = (id[ATA_ID_CFA_MODES] >> 0) & 0x7;
>>>>>> +        int dma = (id[ATA_ID_CFA_MODES] >> 3) & 0x7;
>>>>>>  
>>>>>>          if (pio)
>>>>>>              pio_mask |= (1 << 5);
>>>>>> @@ -2408,7 +2408,8 @@ int ata_dev_configure(struct ata_device      
>>>>>> /* ATA-specific feature tests */
>>>>>>      if (dev->class == ATA_DEV_ATA) {
>>>>>>          if (ata_id_is_cfa(id)) {
>>>>>> -            if (id[162] & 1) /* CPRM may make this media unusable */
>>>>>> +            /* CPRM may make this media unusable */
>>>>>> +            if (id[ATA_ID_CFA_KEY_MGMT] & 1)
>>>>>>                  ata_dev_printk(dev, KERN_WARNING,
>>>>>>                             "supports DRM functions and may "
>>>>>>                             "not be fully accessable.\n");
> 
>>>> This you'll need to resend...
> 
>>>    I wonder why you're telling me this only now
> 
>> Because you asked "have you forgotten about this one?" on April 8th.
> 
>    I mean why didn't you tell me to resubmit when you split off the 
> ata.h part of the original patch? I was under impression that you would 
> queue this part too...

It got lost in the confusion, I suppose.  I figured you would resubmit 
when you posted the IDE version.

If you recall, you requested that this go via Bart's tree on March 3rd. 
  Then Bart did a big push without it.  So, to prevent delaying you 
further, I split off the ata.h patch and forwarded that upstream.

	Jeff




  reply	other threads:[~2009-04-13 17:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 17:29 [PATCH 1/2] libata: add CFA specific identify data words Sergei Shtylyov
2009-03-04  4:56 ` Jeff Garzik
2009-03-04  7:03 ` Jeff Garzik
2009-04-08 11:46 ` Sergei Shtylyov
2009-04-08 13:24   ` Jeff Garzik
2009-04-13 16:48     ` Sergei Shtylyov
2009-04-13 16:51       ` Jeff Garzik
2009-04-13 16:58         ` Sergei Shtylyov
2009-04-13 17:16           ` Jeff Garzik [this message]
2009-04-13 19:42             ` Bartlomiej Zolnierkiewicz
2009-04-13 20:28               ` Jeff Garzik
2009-04-13 21:32                 ` Bartlomiej Zolnierkiewicz

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=49E37385.6070506@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).