linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Darren Stevens <darren@stevens-zone.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata:pata_atiixp: Don't use unconnected secondary port on SB600/SB700
Date: Fri, 20 Jan 2017 15:40:21 -0500	[thread overview]
Message-ID: <20170120204021.GC9280@mtj.duckdns.org> (raw)
In-Reply-To: <497611d4655.7b408682@auth.smtp.1and1.co.uk>

Hello, Darren.

On Fri, Jan 20, 2017 at 06:03:32PM +0000, Darren Stevens wrote:
> The SB600 and SB700 southbridge chips from ATI/AMD only have
> connections for the primary IDE port. As these chips have unique
> pci device ID's use these to mark the secondary port as 'dummy'
> 
> Signed-off-by: Darren Stevens <darren@stevens-zone.net>
> ---
> 
> diff --git a/drivers/ata/pata_atiixp.c b/drivers/ata/pata_atiixp.c
> index 49d705c..588c473 100644
> --- a/drivers/ata/pata_atiixp.c
> +++ b/drivers/ata/pata_atiixp.c
> @@ -278,6 +278,11 @@ static int atiixp_init_one(struct pci_dev *pdev, const
> struct pci_device_id *id)
>     };
>     const struct ata_port_info *ppi[] = { &info, &info };
>  
> +   if((pdev->device == PCI_DEVICE_ID_ATI_IXP600_IDE) ||
        ^
	space here

> +       (pdev->device == PCI_DEVICE_ID_ATI_IXP700_IDE))
> +       /* SB600/700 don't have secondary port wired */

Can you move the comment above if?

> +       ppi[1] = &ata_dummy_port_info;
> +
>     return ata_pci_bmdma_init_one(pdev, ppi, &atiixp_sht, NULL,
>                       ATA_HOST_PARALLEL_SCAN);

And the patch is corrupt.  Attaching the formatted patch might work
better.

Thanks.

-- 
tejun

      reply	other threads:[~2017-01-20 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 18:03 [PATCH] libata:pata_atiixp: Don't use unconnected secondary port on SB600/SB700 Darren Stevens
2017-01-20 20:40 ` Tejun Heo [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=20170120204021.GC9280@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=darren@stevens-zone.net \
    --cc=linux-ide@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).