linux-kernel - Re: [PATCH] ath9k: rename ath9k_platform.h to ath

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]

Date:	Tue, 15 Nov 2011 18:37:08 +0200
From:	Kalle Valo <kvalo@...rom.com>
To:	Sangwook Lee <sangwook.lee@...aro.org>
CC:	linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
	linux-wireless@...r.kernel.org, ath9k-devel@...ts.ath9k.org,
	ralf@...ux-mips.org, juhosg@...nwrt.org, rodrigue@....qualcomm.com,
	linville@...driver.com, rmanohar@....qualcomm.com,
	patches@...aro.org
Subject: Re: [PATCH] ath9k: rename ath9k_platform.h to ath_platform.h

Hi Sangwook,

On 11/15/2011 01:23 PM, Sangwook Lee wrote:
> The patch series proposes to rename ath9k_platform.h to "ath_platform.h
> This header file handles platform data used only for ath9k,
> but it can used by ath6k as well. We can take "wl12xx.h" as
> as a example. Please let us change this file name so that
> other Atheors WLANs use this file for their own platform data

ath9k and ath6kl are very different devices, I'm not sure if sharing a
platfrom struct between the two is really a good idea. Most likely there
is very little the two drivers can share. What are your plans here?

I myself was thinking that we would have include/linux/ath6kl.h
dedicated just for ath6kl. That would makes things simpler.

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