From: Jeff Garzik <jgarzik@pobox.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: netdev@oss.sgi.com, rl@hellgate.ch
Subject: Re: [PATCH] via-rhine: references __init code during resume
Date: Sat, 30 Oct 2004 09:02:42 -0400 [thread overview]
Message-ID: <418390F2.7080901@pobox.com> (raw)
In-Reply-To: <4179543F.1020407@osdl.org>
Randy.Dunlap wrote:
>
>
> ------------------------------------------------------------------------
>
>
> Fix __init section usage:
> rhine_resume calls enable_mmio, so latter cannot be __devinit;
> Error: ./drivers/net/via-rhine.o .text refers to 0000000000000925 R_X86_64_PC32 .init.text+0xfffffffffffffffc
>
> Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
Attaching patches in this way breaks Linus's patch merge scripts (which
I use), causing the description to be completely omitted.
Please include descriptions and patches inline. "sendmail -t < mail"
works well for this. You need only supply the From, To, and Subject
headers, and a blank line, in order for this to work.
Jeff
next prev parent reply other threads:[~2004-10-30 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 18:41 [PATCH] via-rhine: references __init code during resume Randy.Dunlap
2004-10-30 13:02 ` Jeff Garzik [this message]
2004-11-01 17:21 ` Randy.Dunlap
2004-11-05 7:57 ` Jeff Garzik
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=418390F2.7080901@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=rddunlap@osdl.org \
--cc=rl@hellgate.ch \
/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).