From: Esben Nielsen <[EMAIL PROTECTED]>
Date: Tue, 6 Sep 2005 20:56:40 +0200 (METDST)
> Andrew and David: I CC'ed you guyes because you took care of it the last
> time :-)
Applied, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
cnet.c 2005-06-25
> 20:42:46.0 +0200
> +++ linux-2.6.13-gentoo/drivers/net/arcnet/arcnet.c 2005-09-03
> 19:46:54.227846664 +0200
> @@ -597,7 +597,7 @@ static int arcnet_send_packet(struct sk_
> struct ArcProto *proto;
> int txbuf;
> u
because you took care of it the last
time :-)
Esben
url to the patch:
http://pieter.dejaeghere.net:9080/arcnet/patch-buffer
inlined (hopefully without broken linewraps):
--- linux-2.6.12-gentoo-r1/drivers/net/arcnet/arcnet.c2005-06-25
20:42:46.0 +0200
+++ linux-2.6.13-gentoo
From: Esben Nielsen [EMAIL PROTECTED]
Date: Tue, 6 Sep 2005 20:56:40 +0200 (METDST)
Andrew and David: I CC'ed you guyes because you took care of it the last
time :-)
Applied, thanks.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Alan Cox wrote:
On Llu, 2005-09-05 at 14:17 +0600, Alexander E. Patrakov wrote:
Hello,
I tried to build linux-2.6.13-mm1 with the attached configuration, and
it failed with:
drivers/usb/serial/whiteheat.c: In function `rx_data_softint':
drivers/usb/serial/whiteheat.c:1433: error
On Llu, 2005-09-05 at 14:17 +0600, Alexander E. Patrakov wrote:
> Hello,
>
> I tried to build linux-2.6.13-mm1 with the attached configuration, and
> it failed with:
>
> drivers/usb/serial/whiteheat.c: In function `rx_data_softint':
> drivers/usb/serial/whiteheat.c:1433:
On Llu, 2005-09-05 at 14:17 +0600, Alexander E. Patrakov wrote:
Hello,
I tried to build linux-2.6.13-mm1 with the attached configuration, and
it failed with:
drivers/usb/serial/whiteheat.c: In function `rx_data_softint':
drivers/usb/serial/whiteheat.c:1433: error: structure has no member
Alan Cox wrote:
On Llu, 2005-09-05 at 14:17 +0600, Alexander E. Patrakov wrote:
Hello,
I tried to build linux-2.6.13-mm1 with the attached configuration, and
it failed with:
drivers/usb/serial/whiteheat.c: In function `rx_data_softint':
drivers/usb/serial/whiteheat.c:1433: error
On Tue, Aug 30, 2005 at 01:57:27AM +0200, Ricardo Galli wrote:
> 2.6.13 does not boot in my PPC (iBook, 500 MHz), it hangs just at the very
> begining and the machines is automatically rebooted after a couple of
> minutes.
I've filed a bug at kernel bugzilla so your report won't be lost. See
Greg KH wrote:
> On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote:
>
>>Linus Torvalds wrote:
>>
>>>There it is.
>>>
>>>The most painful part of 2.6.13 is likely to be the fact that we made x86
>>>use the generic PCI bus setup code for assigning unassigned resources.
>>>That
Greg KH wrote:
On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote:
Linus Torvalds wrote:
There it is.
The most painful part of 2.6.13 is likely to be the fact that we made x86
use the generic PCI bus setup code for assigning unassigned resources.
That uncovered rather a lot of
On Tue, Aug 30, 2005 at 01:57:27AM +0200, Ricardo Galli wrote:
2.6.13 does not boot in my PPC (iBook, 500 MHz), it hangs just at the very
begining and the machines is automatically rebooted after a couple of
minutes.
I've filed a bug at kernel bugzilla so your report won't be lost. See
Hi.
On Fri, 2005-09-02 at 01:15, Eric W. Biederman wrote:
> Nigel Cunningham <[EMAIL PROTECTED]> writes:
>
> > On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
> >> Meelis Roos wrote:
> >> >
> >> > It's OK then - I'm not using any suspend and I had a problem that my
> >> > machine powered down
Nigel Cunningham <[EMAIL PROTECTED]> writes:
> On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
>> Meelis Roos wrote:
>> >
>> > It's OK then - I'm not using any suspend and I had a problem that my
>> > machine powered down instead of reboot. The patch that went into 2.6.13
>> > after rc7 fixed
On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
> Meelis Roos wrote:
> >
> > It's OK then - I'm not using any suspend and I had a problem that my
> > machine powered down instead of reboot. The patch that went into 2.6.13
> > after rc7 fixed it for me. So the current tree is OK for me and if
Meelis Roos wrote:
>
> It's OK then - I'm not using any suspend and I had a problem that my
> machine powered down instead of reboot. The patch that went into 2.6.13
> after rc7 fixed it for me. So the current tree is OK for me and if it's
> OK for you too after suspend2 changes then this case
I've since found that in the suspend2 code, I was working around this
problem before by not calling the prepare method. I've just today
modified the Suspend code so that it calls prepare for all of the
powerdown methods and everything is working fine without reverting the
patch. I guess this is
Hi.
On Thu, 2005-09-01 at 16:24, Meelis Roos wrote:
> RD> Well, there aren't many differences between 2.6.13-rc7 and 2.6.13. If
> RD> I had to guess, I would bet the commit below is what broke you. I'm
> RD> including a patch that reverts it at the end of this email
>
> Nigel, have you tried
Hi All,
An update of the uClinux (MMU-less) fixups against 2.6.13.
Strait forward merge of the current outstanding patchs from
2.6.12-uc0. A few updates and fixes, but not alot of change in
this one.
http://www.uclinux.org/pub/uClinux/uClinux-2.6.x/linux-2.6.13-uc0.patch.gz
Change log
RD> Well, there aren't many differences between 2.6.13-rc7 and 2.6.13. If
RD> I had to guess, I would bet the commit below is what broke you. I'm
RD> including a patch that reverts it at the end of this email
Nigel, have you tried reverting the patch Roland pointed out? It
probably helps you.
RD Well, there aren't many differences between 2.6.13-rc7 and 2.6.13. If
RD I had to guess, I would bet the commit below is what broke you. I'm
RD including a patch that reverts it at the end of this email
Nigel, have you tried reverting the patch Roland pointed out? It
probably helps you.
I
Hi.
On Thu, 2005-09-01 at 16:24, Meelis Roos wrote:
RD Well, there aren't many differences between 2.6.13-rc7 and 2.6.13. If
RD I had to guess, I would bet the commit below is what broke you. I'm
RD including a patch that reverts it at the end of this email
Nigel, have you tried reverting
I've since found that in the suspend2 code, I was working around this
problem before by not calling the prepare method. I've just today
modified the Suspend code so that it calls prepare for all of the
powerdown methods and everything is working fine without reverting the
patch. I guess this is
Meelis Roos wrote:
It's OK then - I'm not using any suspend and I had a problem that my
machine powered down instead of reboot. The patch that went into 2.6.13
after rc7 fixed it for me. So the current tree is OK for me and if it's
OK for you too after suspend2 changes then this case can
On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
Meelis Roos wrote:
It's OK then - I'm not using any suspend and I had a problem that my
machine powered down instead of reboot. The patch that went into 2.6.13
after rc7 fixed it for me. So the current tree is OK for me and if it's
OK
Nigel Cunningham [EMAIL PROTECTED] writes:
On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
Meelis Roos wrote:
It's OK then - I'm not using any suspend and I had a problem that my
machine powered down instead of reboot. The patch that went into 2.6.13
after rc7 fixed it for me. So the
Hi.
On Fri, 2005-09-02 at 01:15, Eric W. Biederman wrote:
Nigel Cunningham [EMAIL PROTECTED] writes:
On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
Meelis Roos wrote:
It's OK then - I'm not using any suspend and I had a problem that my
machine powered down instead of reboot.
On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote:
> Linus Torvalds wrote:
> > There it is.
> >
> > The most painful part of 2.6.13 is likely to be the fact that we made x86
> > use the generic PCI bus setup code for assigning unassigned resources.
> > That uncovered rather a lot
Hi,
the description of PCI_NAMES is conflicting with its default option (now
N/y/? instead of Y/n/?). Here is a small patch that should remove the
confusion in drivers/pci/Kconfig.
Regards,
Alexandre
Signed-off-by : Alexandre Buisse <[EMAIL PROTECTED]>
--- drivers/pci/Kconfig.old 2005-08-31
Hi,
the description of PCI_NAMES is conflicting with its default option (now
N/y/? instead of Y/n/?). Here is a small patch that should remove the
confusion in drivers/pci/Kconfig.
Regards,
Alexandre
Signed-off-by : Alexandre Buisse [EMAIL PROTECTED]
--- drivers/pci/Kconfig.old 2005-08-31
On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote:
Linus Torvalds wrote:
There it is.
The most painful part of 2.6.13 is likely to be the fact that we made x86
use the generic PCI bus setup code for assigning unassigned resources.
That uncovered rather a lot of nasty
Linus Torvalds wrote:
> There it is.
>
> The most painful part of 2.6.13 is likely to be the fact that we made x86
> use the generic PCI bus setup code for assigning unassigned resources.
> That uncovered rather a lot of nasty small details, but should also mean
> that a lot of laptops in
This patch enables more new hardware.
ACKed-by: Kylene Hall <[EMAIL PROTECTED]>
Forwarded Message
From: Philipp Matthias Hahn <[EMAIL PROTECTED]>
To: Kylene Hall <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: [tpmdd-devel] [PATCH] linux-2.6.13/drivers/ch
On Maw, 2005-08-30 at 11:21 -0400, linux-os (Dick Johnson) wrote:
> we have been starting at 0x30001000. Now, with
> Linux-2.6.13, I see that PCI/Bus resources are
> being allocated on top of this RAM!!! This should
2.6.13 redoes the bus assignments which might have indeed made mem= d
Hello, more problems are being found with linux-2.6.13
Some imaging systems reserve large amounts of
contiguous DMA RAM (16 megabytes) by booting
with 'mem='. In the subject systems, we boot
with "mem=768m" which makes the first available
RAM at 768 * 1024 * 1024 = 0x3000.
Certai
On Tue, 30 Aug 2005, David Hollis wrote:
> On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
> > El Tue, 30 Aug 2005 01:34:25 +0200,
> > Jesper Juhl <[EMAIL PROTECTED]> escribió:
> >
> > > I don't see why we should break a bunch of drivers by doing that.
> > > Much better, in my oppinion,
On Tue, Aug 30, 2005 at 10:28:37AM -0400, David Hollis wrote:
> On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
> > El Tue, 30 Aug 2005 01:34:25 +0200,
> > Jesper Juhl <[EMAIL PROTECTED]> escribió:
> >
> > > I don't see why we should break a bunch of drivers by doing that.
> > > Much
On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
> El Tue, 30 Aug 2005 01:34:25 +0200,
> Jesper Juhl <[EMAIL PROTECTED]> escribió:
>
> > I don't see why we should break a bunch of drivers by doing that.
> > Much better, in my oppinion, to fix the few remaining drivers still
> > using
Changes in "request_mem_region()" ("__request_region()")
now seem to force PCI/Bus alignment upon the requested region.
It appears as though somebody thought this would only used
to reserve address-space on a PCI/Bus.
Linux-2.6.12.5 and all known previous versions back to
linux-2.4.26 worked
Le Tuesday 30 August 2005 a 01:08, Stephane Wirtel ecrivait:
> Hi,
>
> By compiling my kernel, I can see that the __check_region function (in
> kernel/resource.c) is deprecated.
>
> With a grep on the source code of the last release, I get this result.
>
> drivers/pnp/resource.c:255:
Le Tuesday 30 August 2005 a 01:08, Stephane Wirtel ecrivait:
Hi,
By compiling my kernel, I can see that the __check_region function (in
kernel/resource.c) is deprecated.
With a grep on the source code of the last release, I get this result.
drivers/pnp/resource.c:255: if
Changes in request_mem_region() (__request_region())
now seem to force PCI/Bus alignment upon the requested region.
It appears as though somebody thought this would only used
to reserve address-space on a PCI/Bus.
Linux-2.6.12.5 and all known previous versions back to
linux-2.4.26 worked fine.
On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
El Tue, 30 Aug 2005 01:34:25 +0200,
Jesper Juhl [EMAIL PROTECTED] escribió:
I don't see why we should break a bunch of drivers by doing that.
Much better, in my oppinion, to fix the few remaining drivers still
using check_region and
On Tue, Aug 30, 2005 at 10:28:37AM -0400, David Hollis wrote:
On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
El Tue, 30 Aug 2005 01:34:25 +0200,
Jesper Juhl [EMAIL PROTECTED] escribió:
I don't see why we should break a bunch of drivers by doing that.
Much better, in my
On Tue, 30 Aug 2005, David Hollis wrote:
On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
El Tue, 30 Aug 2005 01:34:25 +0200,
Jesper Juhl [EMAIL PROTECTED] escribió:
I don't see why we should break a bunch of drivers by doing that.
Much better, in my oppinion, to fix the few
Hello, more problems are being found with linux-2.6.13
Some imaging systems reserve large amounts of
contiguous DMA RAM (16 megabytes) by booting
with 'mem='. In the subject systems, we boot
with mem=768m which makes the first available
RAM at 768 * 1024 * 1024 = 0x3000.
Certain versions
On Maw, 2005-08-30 at 11:21 -0400, linux-os (Dick Johnson) wrote:
we have been starting at 0x30001000. Now, with
Linux-2.6.13, I see that PCI/Bus resources are
being allocated on top of this RAM!!! This should
2.6.13 redoes the bus assignments which might have indeed made mem= do
totally
This patch enables more new hardware.
ACKed-by: Kylene Hall [EMAIL PROTECTED]
Forwarded Message
From: Philipp Matthias Hahn [EMAIL PROTECTED]
To: Kylene Hall [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [tpmdd-devel] [PATCH] linux-2.6.13/drivers/char/tpm/tpm_atmel.c
on ICH6
Linus Torvalds wrote:
There it is.
The most painful part of 2.6.13 is likely to be the fact that we made x86
use the generic PCI bus setup code for assigning unassigned resources.
That uncovered rather a lot of nasty small details, but should also mean
that a lot of laptops in particular
Yes. I did also report it (see http://lkml.org/lkml/2005/8/26/252)
cheers,
Masoud Sharbiani
Lee Revell wrote:
On Mon, 2005-08-29 at 14:23 -0400, Masoud Sharbiani wrote:
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled
On 8/30/05, Diego Calleja <[EMAIL PROTECTED]> wrote:
> El Tue, 30 Aug 2005 01:34:25 +0200,
> Jesper Juhl <[EMAIL PROTECTED]> escribió:
>
> > I don't see why we should break a bunch of drivers by doing that.
> > Much better, in my oppinion, to fix the few remaining drivers still
> > using
> There it is.
2.6.13 does not boot in my PPC (iBook, 500 MHz), it hangs just at the very
begining and the machines is automatically rebooted after a couple of
minutes.
The on-screen messages finishes with a few "openpic" messages:
http://mnm.uib.es/gallir/tmp/linux-13-ppc.jpg
I used the
El Tue, 30 Aug 2005 01:34:25 +0200,
Jesper Juhl <[EMAIL PROTECTED]> escribió:
> I don't see why we should break a bunch of drivers by doing that.
> Much better, in my oppinion, to fix the few remaining drivers still
> using check_region and *then* kill it. Even unmaintained drivers may
I'd
On 8/30/05, Diego Calleja <[EMAIL PROTECTED]> wrote:
[snip]
>
> /me wonders why check_region has not been killed, it has been
> deprecated for years; killing it would force developers to fix it
> and would help to identify unmaintained drivers...
I don't see why we should break a bunch of
El Tue, 30 Aug 2005 01:14:17 +0200,
Stephane Wirtel <[EMAIL PROTECTED]> escribió:
> Is there a function to replace this deprecated function ?
request_region
> Why is it deprecated ?
>From http://lists.osdl.org/pipermail/kernel-janitors/2004-January/000346.html:
"The reason that check_region()
On 8/30/05, Stephane Wirtel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> By compiling my kernel, I can see that the __check_region function (in
> kernel/resource.c) is deprecated.
>
[snip]
>
> Is there a function to replace this deprecated function ?
>
Yes, you just call request_region() and check its
On Tue, 30 Aug 2005, Stephane Wirtel wrote:
> Hi,
>
> By compiling my kernel, I can see that the __check_region function (in
> kernel/resource.c) is deprecated.
>
> With a grep on the source code of the last release, I get this result.
>
> drivers/pnp/resource.c:255: if
On Mon, 2005-08-29 at 14:23 -0400, Masoud Sharbiani wrote:
> Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
> dual P3 machine
> It works just fine when compiled UP.
> This bug did NOT exist on 2.6.13-rc6 version.
Did you discover this bug with 2.6.13-rc7 before 2.6.13 was
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled UP.
This bug did NOT exist on 2.6.13-rc6 version.
Through a serial console I captured the following:
---
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
On Mon, 29 Aug 2005, Antonino A. Daplas wrote:
>
> Both, actually, with exactly the same patch. In the long changelog, both
> Steven and Paul are co-signees but only Paul's name appeared in the short
> changelog.
git only has one author field. That's not really technically fundamental
(git
On Mon, 2005-08-29 at 22:25 +0800, Antonino A. Daplas wrote:
> Nigel Cunningham wrote:
> > Hi.
> >
> > On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
> >> On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
> >>
> >>> Paul Mackerras:
> >>> Remove race between con_open and con_close
>
Nigel Cunningham wrote:
Hi.
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
Paul Mackerras:
Remove race between con_open and con_close
Hey, I'm the first to report this with the fix and Paul gets the credit?
I guess I'll crawl
> "Nigel" == Nigel Cunningham <[EMAIL PROTECTED]> writes:
Nigel> Hi. I have a couple of reports of powering off being
Nigel> broken between 2.6.13-rc7 and 2.6.13 :( (One my computer
Nigel> and one a Suspend2 user). I'll happily test patches.
Well, there aren't many differences
On Fri, Aug 26, 2005 at 09:33:29PM -0700, Deepak Saxena wrote:
> On Aug 25 2005, at 16:04, Erik Mouw was caught saying:
> > On Tue, Aug 23, 2005 at 10:08:13PM -0700, Linus Torvalds wrote:
> > > I really wanted to release a 2.6.13, but there's been enough changes
> > > while we've been waiting
Hi.
On Mon, 2005-08-29 at 22:25, Jörn Engel wrote:
> On Mon, 29 August 2005 22:17:30 +1000, Nigel Cunningham wrote:
> > On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
> > > On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
> > >
> > > >
> > > > Paul Mackerras:
> > > > Remove race
On Mon, 29 August 2005 22:17:30 +1000, Nigel Cunningham wrote:
> On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
> > On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
> >
> > >
> > > Paul Mackerras:
> > > Remove race between con_open and con_close
> >
> > Hey, I'm the first to
Hi.
I have a couple of reports of powering off being broken between
2.6.13-rc7 and 2.6.13 :( (One my computer and one a Suspend2 user). I'll
happily test patches.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
-
To
Hi.
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
> On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
>
> >
> > Paul Mackerras:
> > Remove race between con_open and con_close
>
> Hey, I'm the first to report this with the fix and Paul gets the credit?
> I guess I'll crawl back to
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
>
> Paul Mackerras:
> Remove race between con_open and con_close
Hey, I'm the first to report this with the fix and Paul gets the credit?
I guess I'll crawl back to my little world (RT) where they actually
appreciate me. :-(
;-)
--
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
Paul Mackerras:
Remove race between con_open and con_close
Hey, I'm the first to report this with the fix and Paul gets the credit?
I guess I'll crawl back to my little world (RT) where they actually
appreciate me. :-(
;-)
--
Hi.
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
Paul Mackerras:
Remove race between con_open and con_close
Hey, I'm the first to report this with the fix and Paul gets the credit?
I guess I'll crawl back to my little
Hi.
I have a couple of reports of powering off being broken between
2.6.13-rc7 and 2.6.13 :( (One my computer and one a Suspend2 user). I'll
happily test patches.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
-
To
On Mon, 29 August 2005 22:17:30 +1000, Nigel Cunningham wrote:
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
Paul Mackerras:
Remove race between con_open and con_close
Hey, I'm the first to report this with the
Hi.
On Mon, 2005-08-29 at 22:25, Jörn Engel wrote:
On Mon, 29 August 2005 22:17:30 +1000, Nigel Cunningham wrote:
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
Paul Mackerras:
Remove race between con_open and
On Fri, Aug 26, 2005 at 09:33:29PM -0700, Deepak Saxena wrote:
On Aug 25 2005, at 16:04, Erik Mouw was caught saying:
On Tue, Aug 23, 2005 at 10:08:13PM -0700, Linus Torvalds wrote:
I really wanted to release a 2.6.13, but there's been enough changes
while we've been waiting for other
Nigel Cunningham wrote:
Hi.
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
Paul Mackerras:
Remove race between con_open and con_close
Hey, I'm the first to report this with the fix and Paul gets the credit?
I guess I'll crawl
On Mon, 2005-08-29 at 22:25 +0800, Antonino A. Daplas wrote:
Nigel Cunningham wrote:
Hi.
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
Paul Mackerras:
Remove race between con_open and con_close
Hey, I'm the first to
On Mon, 29 Aug 2005, Antonino A. Daplas wrote:
Both, actually, with exactly the same patch. In the long changelog, both
Steven and Paul are co-signees but only Paul's name appeared in the short
changelog.
git only has one author field. That's not really technically fundamental
(git
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled UP.
This bug did NOT exist on 2.6.13-rc6 version.
Through a serial console I captured the following:
---
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
On Mon, 2005-08-29 at 14:23 -0400, Masoud Sharbiani wrote:
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled UP.
This bug did NOT exist on 2.6.13-rc6 version.
Did you discover this bug with 2.6.13-rc7 before 2.6.13 was
On Tue, 30 Aug 2005, Stephane Wirtel wrote:
Hi,
By compiling my kernel, I can see that the __check_region function (in
kernel/resource.c) is deprecated.
With a grep on the source code of the last release, I get this result.
drivers/pnp/resource.c:255: if
On 8/30/05, Stephane Wirtel [EMAIL PROTECTED] wrote:
Hi,
By compiling my kernel, I can see that the __check_region function (in
kernel/resource.c) is deprecated.
[snip]
Is there a function to replace this deprecated function ?
Yes, you just call request_region() and check its return
El Tue, 30 Aug 2005 01:14:17 +0200,
Stephane Wirtel [EMAIL PROTECTED] escribió:
Is there a function to replace this deprecated function ?
request_region
Why is it deprecated ?
From http://lists.osdl.org/pipermail/kernel-janitors/2004-January/000346.html:
The reason that check_region() is
On 8/30/05, Diego Calleja [EMAIL PROTECTED] wrote:
[snip]
/me wonders why check_region has not been killed, it has been
deprecated for years; killing it would force developers to fix it
and would help to identify unmaintained drivers...
I don't see why we should break a bunch of drivers by
El Tue, 30 Aug 2005 01:34:25 +0200,
Jesper Juhl [EMAIL PROTECTED] escribió:
I don't see why we should break a bunch of drivers by doing that.
Much better, in my oppinion, to fix the few remaining drivers still
using check_region and *then* kill it. Even unmaintained drivers may
I'd usually
There it is.
2.6.13 does not boot in my PPC (iBook, 500 MHz), it hangs just at the very
begining and the machines is automatically rebooted after a couple of
minutes.
The on-screen messages finishes with a few openpic messages:
http://mnm.uib.es/gallir/tmp/linux-13-ppc.jpg
I used the same
On 8/30/05, Diego Calleja [EMAIL PROTECTED] wrote:
El Tue, 30 Aug 2005 01:34:25 +0200,
Jesper Juhl [EMAIL PROTECTED] escribió:
I don't see why we should break a bunch of drivers by doing that.
Much better, in my oppinion, to fix the few remaining drivers still
using check_region and
Yes. I did also report it (see http://lkml.org/lkml/2005/8/26/252)
cheers,
Masoud Sharbiani
Lee Revell wrote:
On Mon, 2005-08-29 at 14:23 -0400, Masoud Sharbiani wrote:
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled
On Mon, 29 Aug 2005, Jerome Pinot wrote:
>
> Using git in the linus tree:
> $ git-whatchanged v2.6.12..v2.6.13 --pretty=full
It's really much nicer to just do
git log --no-merges v2.6.12..v2.6.13
which gives you a much more readable result.
git-whatchanged is useful if you also want
On Mon, 29 Aug 2005, Jesper Juhl wrote:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
> be the 2.6.13-rc7 -> 2.6.13 final ChangeLog. Any chance we could get
> the full 2.6.12 -> 2.6.13 ChangeLog up there?
Done.
(Well, it's going to take a while to mirror out).
>On 8/29/05, Linus Torvalds <...> wrote:
>>
>> There it is.
>>
>http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
>be the 2.6.13-rc7 -> 2.6.13 final ChangeLog. Any chance we could get
>the full 2.6.12 -> 2.6.13 ChangeLog up there?
Using git in the linus tree:
$
On 8/29/05, Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> There it is.
>
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
be the 2.6.13-rc7 -> 2.6.13 final ChangeLog. Any chance we could get
the full 2.6.12 -> 2.6.13 ChangeLog up there?
--
Jesper Juhl <[EMAIL PROTECTED]>
There it is.
The most painful part of 2.6.13 is likely to be the fact that we made x86
use the generic PCI bus setup code for assigning unassigned resources.
That uncovered rather a lot of nasty small details, but should also mean
that a lot of laptops in particular should be able to discover
There it is.
The most painful part of 2.6.13 is likely to be the fact that we made x86
use the generic PCI bus setup code for assigning unassigned resources.
That uncovered rather a lot of nasty small details, but should also mean
that a lot of laptops in particular should be able to discover
On 8/29/05, Linus Torvalds [EMAIL PROTECTED] wrote:
There it is.
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
be the 2.6.13-rc7 - 2.6.13 final ChangeLog. Any chance we could get
the full 2.6.12 - 2.6.13 ChangeLog up there?
--
Jesper Juhl [EMAIL PROTECTED]
Don't
On 8/29/05, Linus Torvalds ... wrote:
There it is.
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
be the 2.6.13-rc7 - 2.6.13 final ChangeLog. Any chance we could get
the full 2.6.12 - 2.6.13 ChangeLog up there?
Using git in the linus tree:
$ git-whatchanged
On Mon, 29 Aug 2005, Jesper Juhl wrote:
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
be the 2.6.13-rc7 - 2.6.13 final ChangeLog. Any chance we could get
the full 2.6.12 - 2.6.13 ChangeLog up there?
Done.
(Well, it's going to take a while to mirror out).
That's
On Mon, 29 Aug 2005, Jerome Pinot wrote:
Using git in the linus tree:
$ git-whatchanged v2.6.12..v2.6.13 --pretty=full
It's really much nicer to just do
git log --no-merges v2.6.12..v2.6.13
which gives you a much more readable result.
git-whatchanged is useful if you also want to
I hate responding to myself but it's necessary:
>RC7-GIT7 barfed on me after some 20 hours:
complete serial console message before it reset is on:
http://newsgate.newsserver.nl/kernel/
as is config-file.
Hardware: AMD64 running pure-64 debian ony tyan motherboard with opteron
250
>I Wrote:
>After 53 hours and 31 minutes it crashed.
>dth pts/1zaphod.dth.net Wed Aug 24 09:54 - crash (2+05:31)
>reboot system boot 2.6.13-rc7 Wed Aug 24 09:51 (2+05:41)
>
>Prior to this kernel it had been running 2.6.12-mm1 without problems:
>reboot system boot
1 - 100 of 390 matches
Mail list logo
