From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755846Ab0CEUOh (ORCPT ); Fri, 5 Mar 2010 15:14:37 -0500 Received: from mail-fx0-f219.google.com ([209.85.220.219]:34124 "EHLO mail-fx0-f219.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755708Ab0CEUOf (ORCPT ); Fri, 5 Mar 2010 15:14:35 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=LsY5eBJe/1+w3Vuk3ejbEVJW/Bd2ihTM039T23RD4qotoSKeHVXu3yFO9qqNCvf70v BXehYE6xacynHzsaOrEp2W1kyjv5x1U67pNfu3P+hvBLJZBri3XonInwItPXFyDY9ob1 3Lpbw4yDb6bSz4H4o8LCYWIANGzyuMjPvxbIY= From: Bartlomiej Zolnierkiewicz To: Jeff Garzik Subject: Re: [git patches] libata updates for 2.6.34 Date: Fri, 5 Mar 2010 21:12:58 +0100 User-Agent: KMail/1.12.4 (Linux/2.6.33-0.1-desktop; KDE/4.3.5; x86_64; ; ) Cc: Andrew Morton , Linus Torvalds , linux-ide@vger.kernel.org, LKML , Alan Cox References: <20100301202330.GA14977@havoc.gtf.org> <201003051958.24987.bzolnier@gmail.com> <4B915EEF.1040307@garzik.org> In-Reply-To: <4B915EEF.1040307@garzik.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201003052112.58271.bzolnier@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 05 March 2010 08:43:43 pm Jeff Garzik wrote: > On 03/05/2010 01:58 PM, Bartlomiej Zolnierkiewicz wrote: > > On Monday 01 March 2010 09:23:30 pm Jeff Garzik wrote: > > > >> libata: Pass host flags into the pci helper > > > > It introduces a subtle bug: > > > > struct ata_host { > > ... > > unsigned long flags; > > > >> @@ -1642,8 +1643,8 @@ extern int ata_pci_sff_activate_host(struct ata_host *host, > >> irq_handler_t irq_handler, > >> struct scsi_host_template *sht); > >> extern int ata_pci_sff_init_one(struct pci_dev *pdev, > >> - const struct ata_port_info * const * ppi, > >> - struct scsi_host_template *sht, void *host_priv); > >> + const struct ata_port_info * const * ppi, > >> + struct scsi_host_template *sht, void *host_priv, int hflags); > > > > 'int' type is not equal 'unsigned long' one on 64-bit architectures. > > True but largely irrelevant as we will never use more than 32 bits worth > of host flags. > > > > Besides doing it this way is clearly suboptimal as the same effect > > could have been achieved by doing: > > > > extern int __ata_pci_sff_init_one(struct pci_dev *pdev, > > const struct ata_port_info * const *ppi, > > struct scsi_host_template *sht, void *host_priv, > > int hflag); > > static inline int ata_pci_sff_init_one(struct pci_dev *pdev, > > const struct ata_port_info * const *ppi, > > struct scsi_host_template *sht, void *host_priv) > > { > > return __ata_pci_sff_init_one(pdev, ppi, sht, host_priv, 0); > > } > > This is far uglier than simply changing the API. > > > without the need to update all drivers and without breaking pending > > out-of-tree driver patches (yeah, it breaks my pata_ep93xx patches).. > > Every post you include a disclaimer about "my patches are not intended > for upstream" yet you still complain? You've interpreted the disclaimer wrong -- "if you want my patches upstream do it yourself or pay for it cause I have neither time nor interest in an added bureaucracy and clean-yet-buggy mentality".. Lets put things in the right perspective, look at your pull request: 48 files changed, 663 insertions(+), 417 deletions(-) then at Dave's IDE pull request: 52 files changed, 617 insertions(+), 678 deletions(-) and finally at my atang tree (I'm just testing 2.6.33 rebase): 328 files changed, 11528 insertions(+), 14491 deletions(-) This is a whole different scale of changes and you shouldn't be surprised that it requires a bit different set of strategies to handle it effectively.. > Some people are never satisfied... When did it become a bad thing? :) -- Bartlomiej Zolnierkiewicz