From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Keith Owens <kaos@ocs.com.au>
Cc: "Chris Funderburg" <chris@directcommunications.net>,
"Linux-Kernel" <linux-kernel@vger.kernel.org>,
"Justin T. Gibbs" <gibbs@scsiguy.com>
Subject: Re: memcpy in 2.2.19
Date: Fri, 30 Mar 2001 16:01:22 -0400 [thread overview]
Message-ID: <200103302001.f2UK1MMv024840@pincoya.inf.utfsm.cl> (raw)
In-Reply-To: Message from Keith Owens <kaos@ocs.com.au> of "Thu, 29 Mar 2001 23:28:37 PST." <7717.985937317@ocs3.ocs-net>
Keith Owens <kaos@ocs.com.au> said:
> On Fri, 30 Mar 2001 08:04:17 +0100,
> "Chris Funderburg" <chris@directcommunications.net> wrote:
> >drivers/scsi/scsi.a(aic7xxx.o): In function `aic7xxx_load_seeprom':
> >aic7xxx.o(.text+0x116bf): undefined reference to `memcpy'
> Under some circumstances gcc will generate an internal call to
> memcpy(). Alas this bypasses the pre-processor so memcpy is not
> converted to the kernel's internal memcpy code. The cause is normally
> a structure assignment, probably this line.
>
> struct seeprom_config *sc = (struct seeprom_config *) scarray;
Just a pointer initialization.
[...]
> The other possibility I can see is
>
> p->sc = *sc;
>
> try
>
> memcpy(&(p->sc), sc, sizeof(*sc));
--
Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
next prev parent reply other threads:[~2001-03-30 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 7:04 memcpy in 2.2.19 Chris Funderburg
2001-03-30 7:28 ` Keith Owens
2001-03-30 20:01 ` Horst von Brand [this message]
2001-03-30 10:00 ` Jeff Garzik
2001-04-02 7:32 ` Chris Funderburg
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=200103302001.f2UK1MMv024840@pincoya.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--cc=chris@directcommunications.net \
--cc=gibbs@scsiguy.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).