mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23pre6aa2 - some problems [with patches]
Date: Mon, 06 Oct 2003 10:55:17 +1000	[thread overview]
Message-ID: <3F80BD75.1BDCBBA2@eyal.emu.id.au> (raw)
In-Reply-To: <20031005104008.GC1561@velociraptor.random>

Andrea Arcangeli wrote:
> 
> On Sun, Oct 05, 2003 at 01:38:20AM +1000, Eyal Lebedinsky wrote:
> > This is most unusual as -aa patches usually apply clean, but I am
> > encountering a number of build problems.
> 
> > And building i2c-2.7.0 (which I need for sensors) is failing.
> >
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.23-pre6-aa2/kernel/drivers/ie
> > ee1394/pcilynx.o
> > depmod:         i2c_bit_add_bus_Rca543f36
> > depmod:         i2c_transfer_R1dea91d1
> > depmod:         i2c_bit_del_bus_Rdf920b11
> > depmod: *** Unresolved symbols in
[trimmed]
> 
> this looks like if you didn't compile the needed i2c (or maybe it was
> due the lack of a `make dep` first), the above modules (pcilynx bttv
> msp3400) looks innocent.

OK, carefully inspecting the logs explains the above. -aa2 breaks the
build
of i2c-2.7.0, but my script already removed the original i2c modules by
then. The failure is just another static HZ initializer situation.

I think that we need an option to revert HZ to a constant for people
that do not want to fight with this change for now (I am sure there
are other drivers in the wild that will take a while to catch up
with this change even after it makes mainline).

gcc -I/usr/src/linux/include -O2 -DLM_SENSORS -D__KERNEL__ -DMODULE
-fomit-frame
-pointer -DEXPORT_SYMTAB -DMODVERSIONS -include
/usr/src/linux/include/linux/mod
versions.h -c kernel/i2c-philips-par.c -o kernel/i2c-philips-par.o
kernel/i2c-philips-par.c:163: initializer element is not constant
kernel/i2c-philips-par.c:163: (near initialization for
`bit_lp_data.timeout')
kernel/i2c-philips-par.c:172: initializer element is not constant
kernel/i2c-philips-par.c:172: (near initialization for
`bit_lp_data2.timeout')

--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>

      parent reply	other threads:[~2003-10-06  0:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04 10:57 2.4.23pre6aa2 Andrea Arcangeli
2003-10-04 15:38 ` 2.4.23pre6aa2 - some problems [with patches] Eyal Lebedinsky
2003-10-05 10:40   ` Andrea Arcangeli
2003-10-05 11:02     ` Thomas Winischhofer
2003-10-06  0:43     ` Eyal Lebedinsky
2003-10-06  0:55     ` Eyal Lebedinsky [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=3F80BD75.1BDCBBA2@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --cc=andrea@suse.de \
    --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

all inboxes | Powered by JetHome®