linux-kernel - Re: MIPS: BMIPS: broken select on RAW_IRQ

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] [day] [month] [year] [list]

Date:	Mon, 27 Apr 2015 09:11:00 +0200
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	cernekee@...il.com
Cc:	ralf@...ux-mips.org, jaedon.shin@...il.com,
	linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org,
	Paul Bolle <pebolle@...cali.nl>,
	Andreas Ruprecht <rupran@...server.de>,
	hengelein Stefan <stefan.hengelein@....de>
Subject: Re: MIPS: BMIPS: broken select on RAW_IRQ_ACCESSORS

Hi Kevin,

this is just a kind reminder that the issue below is still present and
made its way to v4.1-rc1.

Kind regards,
 Valentin

On Thu, Mar 26, 2015 at 11:47 AM, Valentin Rothberg
<valentinrothberg@...il.com> wrote:
> Hi Kevin,
>
> your commit dd6d84812b1a ("MIPS: BMIPS: Enable additional peripheral
> and CPU support in defconfig") adds a select on the Kconfig symbol
> RAW_IRQ_ACCESORS.   However, this symbol is not defined in Kconfig so
> that the select turns out to be a NOOP.
>
> Is there a patch scheduled somewhere to add this symbol to Kconfig?
>
> I detected this issue with ./scripts/checkkconfigsymbols.py.  Since
> commit b1a3f243485f ("checkkconfigsymbols.py: make it Git aware") the
> script can check and diff specified Git commits.  I found
> RAW_IRQ_ACCESORS by diffing yesterday's and today's next trees (--diff
> commit..commit2).
>
> Kind regards,
>  Valentin
--
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/