public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg@redhat.com>
To: "Håkon Løvdal" <hlovdal@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-scsi@vger.kernel.org,
	James.Bottomley@hansenpartnership.com, shaohua.li@intel.com,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/3] libata: Bind the Linux device tree to the ACPI device tree
Date: Thu, 6 Aug 2009 15:51:25 +0100	[thread overview]
Message-ID: <20090806145125.GB3181@srcf.ucam.org> (raw)
In-Reply-To: <a01a16b50908052354h28522bafja255c4fcac9a2ea8@mail.gmail.com>

On Thu, Aug 06, 2009 at 08:54:31AM +0200, Håkon Løvdal wrote:
> Maybe I am missing something, but wouldn't it be more natural to write this as
> 
>         if (sata_pmp_attached(ap))
>                 adr = SATA_ADR(ap->port_no, dev->link->pmp);
>         else
>                 adr = SATA_ADR(ap->port_no, NO_PORT_MULT);

Heh, yes. That would also work.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-08-06 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 21:03 [PATCH 1/3] SCSI: Allow platform-specific code to be run against the SCSI tree Matthew Garrett
2009-07-13 21:03 ` [PATCH 2/3] libata: Bind the Linux device tree to the ACPI device tree Matthew Garrett
2009-07-13 21:03   ` [PATCH 3/3] libata: Migrate ACPI code over to new bindings Matthew Garrett
2009-08-06  6:54   ` [PATCH 2/3] libata: Bind the Linux device tree to the ACPI device tree Håkon Løvdal
2009-08-06 14:51     ` Matthew Garrett [this message]
2009-08-10 13:38 ` [PATCH 1/3] SCSI: Allow platform-specific code to be run against the SCSI tree Matthew Garrett
2009-08-10 14:55   ` James Bottomley
2009-08-10 14:58     ` Matthew Garrett
2009-08-10 16:03       ` James Bottomley
2009-08-10 16:11         ` Matthew Garrett

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=20090806145125.GB3181@srcf.ucam.org \
    --to=mjg@redhat.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=hlovdal@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=shaohua.li@intel.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