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

Message-ID: <CAJiQ=7DxwwWFts_ckcsusxRgTW+FYd2S32pgj48Pb2xYqKJ8LA@mail.gmail.com>
Date:	Thu, 26 Mar 2015 06:41:36 -0700
From:	Kevin Cernekee <cernekee@...il.com>
To:	Valentin Rothberg <valentinrothberg@...il.com>
Cc:	Ralf Baechle <ralf@...ux-mips.org>,
	Jaedon Shin <jaedon.shin@...il.com>,
	Linux MIPS Mailing List <linux-mips@...ux-mips.org>,
	"linux-kernel@...r.kernel.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

On Thu, Mar 26, 2015 at 3: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?

Oops, that is left over from an earlier attempt at getting the irqchip
drivers to run on 3384 in BE mode:

http://patchwork.linux-mips.org/patch/8254/

We wound up configuring this through DT rather than Kconfig.

Ralf, would you prefer an incremental patch or a whole new submission?
--
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/