linux-kernel - Fix Me in file gpmc-onenand.c

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

Message-ID: <CAPDOMVhMeqHzRsae-TqeNsO2hQF9gE9au9y2oMPohVHOXrs70A@mail.gmail.com>
Date:	Sun, 13 Jul 2014 17:06:20 -0400
From:	Nick Krause <xerofoify@...il.com>
To:	khilman@...prootsystems.com
Cc:	Tony Lindgren <tony@...mide.com>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Fix Me in file gpmc-onenand.c

Hey Kevin,
I am using cscope to find fix mes in the latest git kernels that still
need cleanup. Furthermore  I seem to hitting one in a that file that
you maintain.
Due to this I am wondering should I remove this code or does it still
need to be in the mainline kernel and what mach-omap2 cpus does it
check for.
to support with this if statement.  I am pasting the FiXME and the
code that code around it.
Cheers Nick
else {
               /*
                * FIXME: Appears to be legacy code from initial ONENAND commit.
                 * Unclear what boards this is for and if this can be removed.
                 */
               if (!cpu_is_omap34xx())
                       onenand_sync.wait_on_read = true;
         }
--
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/