On Tue, 31 Jul 2007 11:25:26 +0900 Fernando Luis Vázquez Cao <[EMAIL
PROTECTED]> wrote:
> > runtime. Some drivers don't get used by many people and users of some
> > architectures (esp embedded) tend to lag kernel.org by a long time. So it
> > could be years before all the fallout from this
On Mon, 2007-07-30 at 11:22 -0700, Andrew Morton wrote:
> On Mon, 30 Jul 2007 18:58:14 +0900
> Fernando Luis V__zquez Cao <[EMAIL PROTECTED]> wrote:
>
> > >
> > > So bad things might happen because of this change. And if they do, they
> > > will take a lng time to be discovered, because
On Mon, 30 Jul 2007 18:58:14 +0900
Fernando Luis V__zquez Cao <[EMAIL PROTECTED]> wrote:
> >
> > So bad things might happen because of this change. And if they do, they
> > will take a lng time to be discovered, because non-shared interrupt
> > handlers tend to dwell in crufty old drivers
On Fri, 2007-07-20 at 14:43 -0700, Andrew Morton wrote:
> On Fri, 20 Jul 2007 11:20:43 +0900
> Fernando Luis V__zquez Cao <[EMAIL PROTECTED]> wrote:
>
> > With the advent of kdump it is possible that device drivers receive
> > interrupts generated in the context of a previous kernel. Ideally
> >
On Fri, 2007-07-20 at 14:43 -0700, Andrew Morton wrote:
On Fri, 20 Jul 2007 11:20:43 +0900
Fernando Luis V__zquez Cao [EMAIL PROTECTED] wrote:
With the advent of kdump it is possible that device drivers receive
interrupts generated in the context of a previous kernel. Ideally
quiescing
On Mon, 30 Jul 2007 18:58:14 +0900
Fernando Luis V__zquez Cao [EMAIL PROTECTED] wrote:
So bad things might happen because of this change. And if they do, they
will take a lng time to be discovered, because non-shared interrupt
handlers tend to dwell in crufty old drivers which not
On Mon, 2007-07-30 at 11:22 -0700, Andrew Morton wrote:
On Mon, 30 Jul 2007 18:58:14 +0900
Fernando Luis V__zquez Cao [EMAIL PROTECTED] wrote:
So bad things might happen because of this change. And if they do, they
will take a lng time to be discovered, because non-shared
On Tue, 31 Jul 2007 11:25:26 +0900 Fernando Luis Vázquez Cao [EMAIL
PROTECTED] wrote:
runtime. Some drivers don't get used by many people and users of some
architectures (esp embedded) tend to lag kernel.org by a long time. So it
could be years before all the fallout from this change is
On Fri, 20 Jul 2007 11:20:43 +0900
Fernando Luis V__zquez Cao <[EMAIL PROTECTED]> wrote:
> With the advent of kdump it is possible that device drivers receive
> interrupts generated in the context of a previous kernel. Ideally
> quiescing the underlying devices should suffice but not all drivers
On Fri, 20 Jul 2007 11:20:43 +0900
Fernando Luis V__zquez Cao [EMAIL PROTECTED] wrote:
With the advent of kdump it is possible that device drivers receive
interrupts generated in the context of a previous kernel. Ideally
quiescing the underlying devices should suffice but not all drivers do
With the advent of kdump it is possible that device drivers receive
interrupts generated in the context of a previous kernel. Ideally
quiescing the underlying devices should suffice but not all drivers do
this, either because it is not possible or because they did not
contemplate this case. Thus
With the advent of kdump it is possible that device drivers receive
interrupts generated in the context of a previous kernel. Ideally
quiescing the underlying devices should suffice but not all drivers do
this, either because it is not possible or because they did not
contemplate this case. Thus
12 matches
Mail list logo
