From: Andrew Morton <akpm@osdl.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH -mm] BusLogic gcc 4.1 warning fixes
Date: Thu, 11 May 2006 10:12:31 -0700 [thread overview]
Message-ID: <20060511101231.1ef72659.akpm@osdl.org> (raw)
In-Reply-To: <200605101728.k4AHSTIM004411@dwalker1.mvista.com>
Daniel Walker <dwalker@mvista.com> wrote:
>
> This at least makes the used away of the failure .
> ---
>
>
> I just commented out BusLogic_AbortCommand because the code that uses it is
> commented out the same way .. It could just be removed .
>
> Fixes the following warnings,
>
> drivers/scsi/BusLogic.c: In function 'BusLogic_init':
> drivers/scsi/BusLogic.c:2302: warning: ignoring return value of 'scsi_add_host', declared with attribute warn_unused_result
> drivers/scsi/BusLogic.c: At top level:
> drivers/scsi/BusLogic.c:2963: warning: 'BusLogic_AbortCommand' defined but not used
>
> Signed-Off-By: Daniel Walker <dwalker@mvista.com>
>
> Index: linux-2.6.16/drivers/scsi/BusLogic.c
> ===================================================================
> --- linux-2.6.16.orig/drivers/scsi/BusLogic.c
> +++ linux-2.6.16/drivers/scsi/BusLogic.c
> @@ -2299,7 +2299,8 @@ static int __init BusLogic_init(void)
> scsi_host_put(Host);
> } else {
> BusLogic_InitializeHostStructure(HostAdapter, Host);
> - scsi_add_host(Host, HostAdapter->PCI_Device ? &HostAdapter->PCI_Device->dev : NULL);
> + if (scsi_add_host(Host, HostAdapter->PCI_Device ? &HostAdapter->PCI_Device->dev : NULL))
> + printk(KERN_WARNING "BusLogic: scsi_add_host() failed!\n");
> scsi_scan_host(Host);
> BusLogicHostAdapterCount++;
> }
> @@ -2955,6 +2956,7 @@ static int BusLogic_QueueCommand(struct
> }
Methinks that if scsi_add_host() fails we'll need to do more serious things
here - we cannot just go ahead and pretend that it worked.
So it's best to leave the warning there for now.
The appropriate recovery code is just a few lines up from here - reusing
that might be appropriate. And while you're there, this function should
return -Esomething if it failed, rather than pretending to work.
next prev parent reply other threads:[~2006-05-11 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 17:28 Daniel Walker
2006-05-11 17:12 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-11 20:30 Daniel Walker
2006-05-10 2:55 Daniel Walker
2006-05-10 8:26 ` Christoph Hellwig
2006-05-10 10:44 ` Alan Cox
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=20060511101231.1ef72659.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
all inboxes | Powered by JetHome®