From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Kill warnings in 2.6.6
Date: Thu, 20 May 2004 01:10:40 +0000 [thread overview]
Message-ID: <16556.1424.252715.885634@napali.hpl.hp.com> (raw)
In-Reply-To: <E1BQFaq-0003bB-KT@wombat.disy.cse.unsw.edu.au>
Peter> === arch/ia64/kernel/machvec.c 1.7 vs edited == Peter> --- 1.7/arch/ia64/kernel/machvec.c Thu Mar 18 16:57:15 2004
Peter> +++ edited/arch/ia64/kernel/machvec.c Tue May 18 13:00:35 2004
Peter> @@ -61,6 +61,9 @@
Peter> }
Peter> EXPORT_SYMBOL(machvec_timer_interrupt);
Peter>
Peter> +struct device;
Peter> +struct scatterlist;
Peter> +
Peter> void
Peter> machvec_dma_sync_single (struct device *hwdev, dma_addr_t dma_handle, size_t size, int dir)
Where does this get rid of a warning? A driver or something else?
--david
next prev parent reply other threads:[~2004-05-20 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 1:10 Kill warnings in 2.6.6 Peter Chubb
2004-05-19 21:02 ` David Mosberger
2004-05-20 1:10 ` David Mosberger [this message]
2004-05-20 4:55 ` Peter Chubb
2004-05-20 5:10 ` David Mosberger
2004-05-21 20:23 ` David Mosberger
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=16556.1424.252715.885634@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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