From: Tejun Heo <htejun@gmail.com>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
Akira Iguchi <akira2.iguchi@toshiba.co.jp>,
Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, cbe-oss-dev@ozlabs.org
Subject: Re: [PATCH/RFC] Fix build failure for drivers/ata/pata_scc.c
Date: Fri, 11 May 2007 13:56:08 +0200 [thread overview]
Message-ID: <464459D8.1030305@gmail.com> (raw)
In-Reply-To: <20070511064954.GE15955@bakeyournoodle.com>
Tony Breeds wrote:
> The commit d4b2bab4f26345ea1803feb23ea92fbe3f6b77bc added deadline support to
> prereset and reset methods to libbata the pata_scc driver wasn't converted.
> This patch is a naive attempt to bring this driver up to scratch.
>
> Build failures are:
> drivers/ata/pata_scc.c: In function 'scc_pata_prereset':
> drivers/ata/pata_scc.c:870: error: too few arguments to function 'ata_std_prereset'
> drivers/ata/pata_scc.c: In function 'scc_error_handler':
> drivers/ata/pata_scc.c:916: warning: passing argument 2 of 'ata_bmdma_drive_eh' from incompatible pointer type
> drivers/ata/pata_scc.c:916: warning: passing argument 3 of 'ata_bmdma_drive_eh' from incompatible pointer type
> drivers/ata/pata_scc.c: In function 'scc_pata_prereset':
> drivers/ata/pata_scc.c:871: warning: control reaches end of non-void function
>
> On a releated note scc_bus_post_reset() is (AFACT) identical to
> ata_bus_post_reset(), would a patch to make ata_bus_post_reset() assesable to
> drivers be accepted?
>
>
> Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
> CC: Tejun Heo <htejun@gmail.com>
> CC: Akira Iguchi <akira2.iguchi@toshiba.co.jp>
> CC: Jeff Garzik <jgarzik@pobox.com>
> CC: linux-ide@vger.kernel.org
Acked-by: Tejun Heo <htejun@gmail.com>
--
tejun
prev parent reply other threads:[~2007-05-11 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 6:49 [PATCH/RFC] Fix build failure for drivers/ata/pata_scc.c Tony Breeds
2007-05-11 11:56 ` 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=464459D8.1030305@gmail.com \
--to=htejun@gmail.com \
--cc=akira2.iguchi@toshiba.co.jp \
--cc=cbe-oss-dev@ozlabs.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@bakeyournoodle.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;
as well as URLs for NNTP newsgroup(s).