>
> I think I found it -- in my scripts. :)
> They still think that $ARCH is i386 or x86_64, not "x86".
> I'm testing a fix for that now.
Good - thanks for reporting back.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Thu, 1 Nov 2007 06:21:45 +0100 Sam Ravnborg wrote:
> On Wed, Oct 31, 2007 at 06:39:00PM -0700, Randy Dunlap wrote:
> > Hi Sam,
> >
> > I have daily/nightly builds + test runs that use something like:
> > (but more complicated than this)
> >
> > cp saved.config.file arch/$ARCH/config.default
On Thu, 1 Nov 2007 06:21:45 +0100 Sam Ravnborg wrote:
On Wed, Oct 31, 2007 at 06:39:00PM -0700, Randy Dunlap wrote:
Hi Sam,
I have daily/nightly builds + test runs that use something like:
(but more complicated than this)
cp saved.config.file arch/$ARCH/config.default
EXPORT
I think I found it -- in my scripts. :)
They still think that $ARCH is i386 or x86_64, not x86.
I'm testing a fix for that now.
Good - thanks for reporting back.
Sam
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Wed, Oct 31, 2007 at 06:39:00PM -0700, Randy Dunlap wrote:
> Hi Sam,
>
> I have daily/nightly builds + test runs that use something like:
> (but more complicated than this)
>
> cp saved.config.file arch/$ARCH/config.default
> EXPORT KBUILD_DEFCONFIG=config.default
> make defconfig
On Wed, Oct 31, 2007 at 06:39:00PM -0700, Randy Dunlap wrote:
Hi Sam,
I have daily/nightly builds + test runs that use something like:
(but more complicated than this)
cp saved.config.file arch/$ARCH/config.default
EXPORT KBUILD_DEFCONFIG=config.default
make defconfig
KBUILD_DEFCONFIG
Am 20.02.2007 15:59 schrieb Adrian Bunk:
> I'm usually someone who likes to avoid including unneeded code in the
> kernel, but in this case I'd say KISS - and build it always into the
> gigaset module.
There seems to be a clear majority for this solution. So KISS it
will be. Thanks for all the
On Tue, Feb 20, 2007 at 02:56:27PM +0100, Tilman Schmidt wrote:
> Adrian Bunk schrieb:
> > On Sun, Feb 18, 2007 at 12:22:10AM -0500, Kai Germaschewski wrote:
> >> On Sat, 17 Feb 2007, Tilman Schmidt wrote:
> >>
> >> > asyncdata.o is only needed for M105 and M101, not for the base
> >> > driver.
On Tue, Feb 20, 2007 at 02:56:27PM +0100, Tilman Schmidt wrote:
> > One disadvantage of this approach is that in a kernel with
> > CONFIG_GIGASET_BASE=y, you can't later compile and load the usb_gigaset
> > or ser_gigaset modules without rebooting since they require a change to
> > the kernel
Adrian Bunk schrieb:
> On Sun, Feb 18, 2007 at 12:22:10AM -0500, Kai Germaschewski wrote:
>> On Sat, 17 Feb 2007, Tilman Schmidt wrote:
>>
>> > asyncdata.o is only needed for M105 and M101, not for the base
>> > driver. How do I express in Kbuild that asyncdata.o is to be added
>> > to gigaset-y
Adrian Bunk schrieb:
On Sun, Feb 18, 2007 at 12:22:10AM -0500, Kai Germaschewski wrote:
On Sat, 17 Feb 2007, Tilman Schmidt wrote:
asyncdata.o is only needed for M105 and M101, not for the base
driver. How do I express in Kbuild that asyncdata.o is to be added
to gigaset-y only if
On Tue, Feb 20, 2007 at 02:56:27PM +0100, Tilman Schmidt wrote:
One disadvantage of this approach is that in a kernel with
CONFIG_GIGASET_BASE=y, you can't later compile and load the usb_gigaset
or ser_gigaset modules without rebooting since they require a change to
the kernel image.
On Tue, Feb 20, 2007 at 02:56:27PM +0100, Tilman Schmidt wrote:
Adrian Bunk schrieb:
On Sun, Feb 18, 2007 at 12:22:10AM -0500, Kai Germaschewski wrote:
On Sat, 17 Feb 2007, Tilman Schmidt wrote:
asyncdata.o is only needed for M105 and M101, not for the base
driver. How do I express
Am 20.02.2007 15:59 schrieb Adrian Bunk:
I'm usually someone who likes to avoid including unneeded code in the
kernel, but in this case I'd say KISS - and build it always into the
gigaset module.
There seems to be a clear majority for this solution. So KISS it
will be. Thanks for all the
On Sun, Feb 18, 2007 at 12:22:10AM -0500, Kai Germaschewski wrote:
> On Sat, 17 Feb 2007, Tilman Schmidt wrote:
>
> > Alright, then so be it. But that raises another question:
> > asyncdata.o is only needed for M105 and M101, not for the base
> > driver. How do I express in Kbuild that
On Sun, Feb 18, 2007 at 12:22:10AM -0500, Kai Germaschewski wrote:
On Sat, 17 Feb 2007, Tilman Schmidt wrote:
Alright, then so be it. But that raises another question:
asyncdata.o is only needed for M105 and M101, not for the base
driver. How do I express in Kbuild that asyncdata.o is to
On Sat, 17 Feb 2007, Tilman Schmidt wrote:
> Alright, then so be it. But that raises another question:
> asyncdata.o is only needed for M105 and M101, not for the base
> driver. How do I express in Kbuild that asyncdata.o is to be added
> to gigaset-y only if CONFIG_GIGASET_M105 and
Am 17.02.2007 11:52 schrieb Adrian Bunk:
> On Sat, Feb 17, 2007 at 01:04:33AM +0100, Tilman Schmidt wrote:
>> [...] I'd prefer a
>> Makefile which builds modular usb_gigaset.ko and/or ser_gigaset.ko
>> like the present one (including asyncdata.o), but when linking
>> usb-gigaset.o and
On Sat, Feb 17, 2007 at 01:04:33AM +0100, Tilman Schmidt wrote:
> Am 16.02.2007 09:33 schrieb Adrian Bunk:
> >>> ...
> >>> LD drivers/isdn/gigaset/built-in.o
> >>> drivers/isdn/gigaset/ser_gigaset.o: In function `gigaset_m10x_send_skb':
> >>> (.text+0xe50): multiple definition of
On Sat, Feb 17, 2007 at 01:04:33AM +0100, Tilman Schmidt wrote:
Am 16.02.2007 09:33 schrieb Adrian Bunk:
...
LD drivers/isdn/gigaset/built-in.o
drivers/isdn/gigaset/ser_gigaset.o: In function `gigaset_m10x_send_skb':
(.text+0xe50): multiple definition of `gigaset_m10x_send_skb'
Am 17.02.2007 11:52 schrieb Adrian Bunk:
On Sat, Feb 17, 2007 at 01:04:33AM +0100, Tilman Schmidt wrote:
[...] I'd prefer a
Makefile which builds modular usb_gigaset.ko and/or ser_gigaset.ko
like the present one (including asyncdata.o), but when linking
usb-gigaset.o and ser-gigaset.o into
On Sat, 17 Feb 2007, Tilman Schmidt wrote:
Alright, then so be it. But that raises another question:
asyncdata.o is only needed for M105 and M101, not for the base
driver. How do I express in Kbuild that asyncdata.o is to be added
to gigaset-y only if CONFIG_GIGASET_M105 and
22 matches
Mail list logo
