linux-kernel - Re: [PATCH 1/1] atmel-ssc: fix misuse of dev_dbg when requested ssc instance is not found

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:	Fri, 30 Jan 2009 12:54:08 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	Hans-Christian Egtvedt <hans-christian.egtvedt@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Haavard Skinnemoen <haavard.skinnemoen@...el.com>,
	linux-kernel@...r.kernel.org, dbrownell@...rs.sourceforge.net,
	kay.sievers@...y.org, weiyi.huang@...il.com,
	Andrew Victor <avictor.za@...il.com>
Subject: Re: [PATCH 1/1] atmel-ssc: fix misuse of dev_dbg when requested ssc instance is not found

On Fri, Jan 30, 2009 at 10:50:57AM +0100, Hans-Christian Egtvedt wrote:

> 1 sound/soc/atmel/sam9g20_wm8731.c        274 ssc = ssc_request(0);
> 2 sound/soc/atmel/playpaq_wm8510.c        399 ssc = ssc_request(0);
> 3 sound/spi/at73c213.c                    980 chip->ssc = ssc_request(board->ssc_id);

> The two first are a bit suspicious since they hard code id 0.

They are ASoC board drivers so are already entirely specific to one
board (or family of boards).
--
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/