linux-kernel - Re: [PATCH] ARM: OMAP: Modified omap_mux_init

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]

Message-ID: <20101022172120.GH9149@atomide.com>
Date:	Fri, 22 Oct 2010 10:21:20 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	Tim Nordell <tim.nordell@...icpd.com>
Cc:	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: OMAP: Modified omap_mux_init_signal() to take in
 const char *

* Tim Nordell <tim.nordell@...icpd.com> [101021 12:02]:
>  On 10/21/10 13:50, Tim Nordell wrote:
> 
> It looks like by inspection that there could be a couple of things wrong
> with that patch however.  Namely, on the comparison of muxname to
> m0_entry, if they have the same string up to mode0_len, such as
> "dss_data1" and "dss_data12" it'd match there prematurely as it'd stop
> comparing.  Also, a minor display issue on the printk of the new muxname.

Good catch, it would be nice to get those fixed too. Got any patches
for those issues?

Regards,

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