From: Jeff Garzik <jgarzik@pobox.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: fix sparse warnings
Date: Tue, 17 Jan 2006 19:40:43 -0500 [thread overview]
Message-ID: <43CD8E8B.4020700@pobox.com> (raw)
In-Reply-To: <20051225193427.0962fdea.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Question: in patch block 2, what are the semantics of the user <arg>?
> Does it point to an input u8 args[4] which must be immediately followed
> by an output u8 args[4]? That's what it seems to be. Just checking.
>
>
> Fix sparse warnings:
> drivers/scsi/libata-scsi.c:154:15: warning: cast removes address space of expression
> drivers/scsi/libata-scsi.c:204:20: warning: cast removes address space of expression
> drivers/scsi/libata-scsi.c:204:20: warning: incorrect type in argument 1 (different address spaces)
> drivers/scsi/libata-scsi.c:204:20: expected void [noderef] *to<asn:1>
> drivers/scsi/libata-scsi.c:204:20: got void *<noident>
> drivers/scsi/libata-scsi.c:231:15: warning: cast removes address space of expression
Can you resend this and any other non-ACPI patches you have pending, please?
Jeff
prev parent reply other threads:[~2006-01-18 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 3:34 [PATCH] libata: fix sparse warnings Randy.Dunlap
2006-01-18 0:40 ` Jeff Garzik [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=43CD8E8B.4020700@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).