linux-kernel - Re: MIPS: ralink: CONFIG_RALINK_ILL

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, 12 Jan 2015 13:26:33 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	John Crispin <blogic@...nwrt.org>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	Ralf Baechle <ralf@...ux-mips.org>, linux-mips@...ux-mips.org,
	linux-kernel@...r.kernel.org
Subject: Re: MIPS: ralink: CONFIG_RALINK_ILL_ACC?

John,

On Mon, 2014-11-10 at 13:32 +0100, Paul Bolle wrote:
> On Mon, 2014-10-27 at 11:03 +0100, John Crispin wrote:
> > On 27/10/2014 10:54, Paul Bolle wrote:
> > > Your commit 78865eacb4aa ("MIPS: ralink: add illegal access
> > > driver") landed in today's linux-next (ie, next-20141027). That
> > > commit dates back to May 16, 2013! It adds a driver that is built
> > > if CONFIG_RALINK_ILL_ACC is set. But there's no Kconfig symbol
> > > RALINK_ILL_ACC.
> > > 
> > > I assume that patch that adds this symbol is queued somewhere. Is
> > > that correct?
> > 
> > i'll look into it. the commit that move all dts files to a central
> > folder broke some of my patches so i had to rebase them. apparently
> > the bit that adds the symbol got lost.
> 
> (CONFIG_RALINK_ILL_ACC was already gone in next-20141029. So that issue
> is resolved, as far as I care.)

It returned in next-20141114 and then made it into mainline (v3.19-rc1
and later). But there's still no Kconfig symbol RALINK_ILL_ACC. What's
the status of the patch to add it?


Paul Bolle

--
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/