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-next>] [day] [month] [year] [list]
Date:	Mon, 1 Jun 2015 16:51:48 +0200
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	ralf@...ux-mips.org, Paul Bolle <pebolle@...cali.nl>,
	Andreas Ruprecht <andreas.ruprecht@....de>,
	hengelein Stefan <stefan.hengelein@....de>, tglx@...utronix.de,
	jason@...edaemon.net, linux-mips@...ux-mips.org,
	linux-kernel@...r.kernel.org
Subject: MIPS/IRQCHIP: some remainders of IRQ_CPU

Hi Ralf,

your commit 1f1786e60b53 ("MIPS/IRQCHIP: Move irq_chip from arch/mips
to drivers/irqchip.") is in today's linux-next tree (i.e.,
next-20150601).  It renames the Kconfig option IRQ_CPU to
IRQ_MIPS_CPU, but misses to rename a few Kconfig selects (see git
grep) in arch/mips.

If you agree, I can send a trivial patch that renames those remainders?

I detected the issue with ./scripts/checkkconfigsymbols.py by diffing
the last and today's linux tree.

Some advertisement for a small tool I started a few month a go, which
is made for such cases.  With vgrep [1] you can grep for symbols in
the current directory tree and afterwards open specific lines in your
editor.  It's more or less a comfortable wrapper around (git) grep.  I
use it a lot to study source code as well as to manage code changes.
The most prominent user I know is Greg KH who uses it as a replacement
for cgvg.

Kind regards,
 Valentin

[1] https://github.com/vrothberg/vgrep
--
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