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]
Message-ID: <20121101101233.17ffcf5a@skate>
Date:	Thu, 1 Nov 2012 10:12:33 +0100
From:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Rob Herring <robherring2@...il.com>,
	linux-arm-kernel@...ts.infradead.org,
	Thomas Gleixner <tglx@...utronix.de>, arm@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: plat-versatile: move FPGA irq driver to
 drivers/irqchip

Linus,

On Thu, 1 Nov 2012 10:00:19 +0100, Linus Walleij wrote:

> Sounds like a separate patch but surely we can do this. Is Thomas'
> stuff on a branch somewhere that I can then rebase upon to get
> it upstream? I was planning to get this series as such to the
> ARM SoC maintainers soon-ish.

Not at the moment. But do you want me to put that in a branch, and
agglomerate all the related patches (posted by Rob for GIC/VIC and by
you for the FPGA IRQ controller), and then later send a pull request to
Arnd with those changes?

Also, again, the whole point of the initial infrastructure in
drivers/irqchip/ was to avoid adding per-driver header files in
include/linux/irqchip/, so there should at least be a long term plan on
how to remove those headers file, either by moving more platforms to
DT, or my extending the irqchip infrastructure to cover more features.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
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