All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Greg KH <greg@kroah.com>, Matthew Wilcox <matthew@wil.cx>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	pcihpd-discuss@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	Andrew Morton <akpm@linux-foundation.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [Pcihpd-discuss] [PATCH 26/34] PCI: add pci_try_set_mwi
Date: Thu, 12 Jul 2007 07:29:00 -0400	[thread overview]
Message-ID: <4696107C.60104@emulex.com> (raw)
In-Reply-To: <20070711201229.43b71681.randy.dunlap@oracle.com>

I'm agnostic on the change... As long as we get a message somewhere
when the failure is meaningful, I'm fine with this change. I didn't
like setting mwi by the driver anyway - it should have already been
done by the platform.

-- james s


Randy Dunlap wrote:
>>>> --- a/drivers/scsi/lpfc/lpfc_init.c
>>>> +++ b/drivers/scsi/lpfc/lpfc_init.c
>>>> @@ -1578,10 +1578,7 @@ lpfc_pci_probe_one(struct pci_dev *pdev, const struct pci_device_id *pid)
>>>>  	INIT_LIST_HEAD(&phba->fc_nodes);
>>>>  
>>>>  	pci_set_master(pdev);
>>>> -	retval = pci_set_mwi(pdev);
>>>> -	if (retval)
>>>> -		dev_printk(KERN_WARNING, &pdev->dev,
>>>> -			   "Warning: pci_set_mwi returned %d\n", retval);
>>>> +	pci_try_set_mwi(pdev);
>>> Why remove the warning?  Presumably people want to know if pci_set_mwi
>>> failed.
>> Randy, this was your change, right?
> 
> Uh, I think that my thinking was like this:
> 
> pci_try_set_mwi() and pci_set_mwi() are both "try best effort"
> functions.  Neither of them guarantees that pci_set_cacheline_size()
> will succeed.  And in case of serious problems, pci_set_cacheline_size()
> will print a (KERN_DEBUG) message.
> 
> 
> Anyway, I don't mind restoring the former lpfc code if that is what
> should be done.
> 
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
> 

      reply	other threads:[~2007-07-12 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11841968053873-git-send-email-gregkh@suse.de>
     [not found] ` <11841968092270-git-send-email-gregkh@suse.de>
     [not found]   ` <11841968133805-git-send-email-gregkh@suse.de>
     [not found]     ` <11841968172168-git-send-email-gregkh@suse.de>
     [not found]       ` <11841968221388-git-send-email-gregkh@suse.de>
     [not found]         ` <11841968302709-git-send-email-gregkh@suse.de>
     [not found]           ` <11841968341206-git-send-email-gregkh@suse.de>
     [not found]             ` <11841968561560-git-send-email-gregkh@suse.de>
     [not found]               ` <11841968591561-git-send-email-gregkh@suse.de>
     [not found]                 ` <11841968633587-git-send-email-gregkh@suse.de>
2007-07-12  0:01                   ` [Pcihpd-discuss] [PATCH 26/34] PCI: add pci_try_set_mwi Matthew Wilcox
2007-07-12  0:37                     ` Greg KH
2007-07-12  1:27                       ` Randy Dunlap
2007-07-12  3:12                       ` Randy Dunlap
2007-07-12 11:29                         ` James Smart [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=4696107C.60104@emulex.com \
    --to=james.smart@emulex.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.