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: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	bzolnier@gmail.com, linux-ide@vger.kernel.org, gdu@mns.spb.ru
Subject: Re: [PATCH] ide/libata: fix ata_id_is_cfa()
Date: Mon, 26 Jan 2009 15:12:10 -0500	[thread overview]
Message-ID: <497E191A.1040902@pobox.com> (raw)
In-Reply-To: <497E1700.8090206@ru.mvista.com>

Sergei Shtylyov wrote:
> Alan Cox wrote:
> 
>>>>>> +    if (id[ATA_ID_MAJOR_VER] == 0xFFFF)
>>>>>> +        return 0;
>>>>>> +    return (id[ATA_ID_MAJOR_VER] & (1 << v)) ? 1 : 0;
> 
>>>>>   Refer to afa_dev_cf_sata() on how it's done in really optimal way.
> 
>>>> To what ? - there is no ata or afa_dev_cf_sata ?
> 
>>>    Very funny. Meant to be ata_dev_is_sata(), of course.
> 
>> We don't have one of those either - do you mean ata_id_is_sata ? If so
>> then yes that looks like it might be slightly cleaner although its
>> probably one instruction difference from the .s files.
> 
>    That extra *if* cost more than instruction I think.

Either way, this is irrelevant, since this isn't used in any hot path 
that I am aware of... :)

Alan just posted a reasonable explanation in the "The logic is this" 
email, maybe we can reboot the discussion from there?

Responding to a side point, I don't think its a big deal to combine 
fixes and improvements into a single patch, if you are dealing with the 
same few lines of code.  Just make sure the patch description (and/or 
code comment) enumerates the fixes and improvements both...

	Jeff




  reply	other threads:[~2009-01-26 20:12 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 13:15 [PATCH] ide/libata: fix ata_id_is_cfa() Sergei Shtylyov
2009-01-23 13:33 ` Alan Cox
2009-01-23 13:53   ` Sergei Shtylyov
2009-01-23 15:43     ` Alan Cox
2009-01-23 16:30       ` Sergei Shtylyov
2009-01-23 16:41         ` Alan Cox
2009-01-23 17:01           ` Sergei Shtylyov
2009-01-23 17:12             ` Mark Lord
2009-01-23 17:18               ` Sergei Shtylyov
2009-01-23 17:27   ` Sergei Shtylyov
2009-01-23 17:53     ` Alan Cox
2009-01-23 19:13       ` Sergei Shtylyov
2009-01-24 23:06 ` Sergei Shtylyov
2009-01-25 10:50   ` Alan Cox
2009-01-26 11:49     ` Sergei Shtylyov
2009-01-26 12:01       ` Alan Cox
2009-01-26 18:11         ` Sergei Shtylyov
2009-01-26 19:01           ` Alan Cox
2009-01-26 19:25             ` Sergei Shtylyov
2009-01-25 10:52   ` Alan Cox
2009-01-25 19:04   ` Bartlomiej Zolnierkiewicz
2009-01-26 19:32     ` Sergei Shtylyov
2009-01-26 18:47   ` Sergei Shtylyov
2009-01-26 19:08     ` Alan Cox
2009-01-26 19:28       ` Sergei Shtylyov
2009-01-26 19:33         ` Sergei Shtylyov
2009-01-26 19:41           ` Alan Cox
2009-01-26 19:42           ` Alan Cox
2009-01-26 19:56             ` Sergei Shtylyov
2009-01-26 20:01               ` Alan Cox
2009-01-26 20:31                 ` Sergei Shtylyov
2009-01-26 20:59                   ` Sergei Shtylyov
2009-01-26 21:22                     ` Alan Cox
2009-01-26 21:38                       ` Sergei Shtylyov
2009-01-26 21:43                         ` Sergei Shtylyov
2009-01-26 23:28                           ` Sergei Shtylyov
2009-01-26 20:47                 ` Sergei Shtylyov
2009-01-26 19:39         ` Alan Cox
2009-01-26 19:31       ` Sergei Shtylyov
2009-01-26 19:35         ` Alan Cox
2009-01-26 19:45           ` Sergei Shtylyov
2009-01-26 19:54             ` Alan Cox
2009-01-26 20:03               ` Sergei Shtylyov
2009-01-26 20:12                 ` Jeff Garzik [this message]
2009-01-26 20:23                   ` Sergei Shtylyov
2009-01-26 20:33                     ` Alan Cox
2009-01-26 20:41                       ` Sergei Shtylyov
2009-01-26 23:53                       ` Sergei Shtylyov
2009-01-26 20:16                 ` Sergei Shtylyov
2009-01-27 11:29       ` Sergei Shtylyov

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=497E191A.1040902@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=gdu@mns.spb.ru \
    --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).