Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers

The only downside I can think of for dropping pt_regs is that now it's harder
to just find the IRQ handler in a driver ... it's previously been all but
guaranteed that the _only_ use of that type is the IRQ logic.  The upsides
surely outweigh that.

> >  (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
> >      something different depending on whether it's been supplied with a regs
> >      pointer or not.

gaak!  where did that come from?  I'll be surprised if removing
that causes any problem at all.

- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
  - From: Alan Stern <[email protected]>
- Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
  - From: Andrew Morton <[email protected]>

References:
- [PATCH 1/3] IRQ: Typedef the IRQ flow handler function type
  - From: David Howells <[email protected]>
- Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: [linux-pm] [RFC] OMAP1 PM Core, PM Core Implementation 2/2
Next by Date: Re: linux/compat.h includes asm/signal.h causing problems
Previous by thread: Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Next by thread: Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]