Return-path: Received: from nbd.name ([46.4.11.11]:59972 "EHLO nbd.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756356Ab3CMLW4 (ORCPT ); Wed, 13 Mar 2013 07:22:56 -0400 Message-ID: <514060B5.8060301@openwrt.org> (sfid-20130313_122333_624644_FE4EE1BB) Date: Wed, 13 Mar 2013 12:19:17 +0100 From: John Crispin MIME-Version: 1.0 To: Jonas Gorski CC: Paul Bolle , Ivo van Doorn , Gertjan van Wingerde , Helmut Schaa , "John W. Linville" , linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: rt2x00: Kconfig symbols RALINK_RT288X and RALINK_RT305X References: <1363165170.3137.182.camel@x61.thuisdomein> <1363169039.3137.186.camel@x61.thuisdomein> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 13/03/13 11:35, Jonas Gorski wrote: > On 13 March 2013 11:03, Paul Bolle wrote: >> On Wed, 2013-03-13 at 10:51 +0100, Jonas Gorski wrote: >>> The actual accepted Kconfig symbol names are different though, so they >>> should be changed in rt2x00 to match them (SOC_RT288X and SOC_RT305X). >> Thanks. Note that I could not find an actual Kconfig symbol SOC_RT288X! > Ah, yes, the inital submission only included RT305X support, not > RT288X (and neither of the newer chips). These will come later. > >> Anyhow, I guess somebody has the (trivial) patch to convert >> RALINK_RT...X and CONFIG_RALINK_RT...X to their SOC_* equivalents queued >> for inclusion in v3.9-rcX. Is that correct? > Yes, that should be everything. John Crispin, anything missing from that? > > > Jonas > > Hi, I will look into this later this week. John