lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 20 Apr 2008 23:40:08 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Jeff Garzik <jeff@...zik.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk, kernel@...tstofly.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/15] ARM minor irq handler cleanups

On Sun, Apr 20, 2008 at 06:17:32PM -0400, Jeff Garzik wrote:
> Andrew Morton wrote:
> >If we had a migration plan (ie: request_irq_new(), above) then this of
> >course wouldn't be a problem.
> 
> A fair comment...

Then we'll be stuck with request_irq_new() for the next 10 years or so.

FWIW (and appologies for hijacking the topic), Jeffs discussion about
changing the ARM integrator RTC driver has triggered a number of cleanups
in the ARM tree:

- converting the ARM integrator PL030 RTC driver to a RTC class driver

  ... which triggered:

- removal of the ARM dyntick code and the unused generic changes
  (including the s390 and sh bits which look like they've never been
   functional.)

  ... which triggered:

- attempting to fix a circular include dependency involving linux/irq.h
  and asm-arm/mach/irq.h

  ... which then triggered:

- allowing PXA platform class to build for more than one PXA platform
  at a time, so I don't have to run 20 (!) separate kernel builds to
  check them all for breakage caused by the elimination of the
  circular dependency.

  ... which also allowed me to find several PXA platform build bugs.

Thanks Jeff. ;)

I'm not intending pushing this stuff into mainline for a bit, although
it will appear in my public tree for others to start looking at and for
them to be aware of.

That does mean that, unfortunately, akpm's going to see those changes
and it might cause Andrew some headaches - sorry about that.  You may
wish to avoid pulling the ARM 'devel' branch until the dust settles.

(Obviously the appropriate fixes will be head towards Linus at the
appropriate time.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ