Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756323Ab3CMKg0 (ORCPT ); Wed, 13 Mar 2013 06:36:26 -0400 Received: from mail.nanl.de ([217.115.11.12]:52734 "EHLO mail.nanl.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754027Ab3CMKgZ (ORCPT ); Wed, 13 Mar 2013 06:36:25 -0400 MIME-Version: 1.0 In-Reply-To: <1363169039.3137.186.camel@x61.thuisdomein> References: <1363165170.3137.182.camel@x61.thuisdomein> <1363169039.3137.186.camel@x61.thuisdomein> From: Jonas Gorski Date: Wed, 13 Mar 2013 11:35:31 +0100 Message-ID: Subject: Re: rt2x00: Kconfig symbols RALINK_RT288X and RALINK_RT305X To: Paul Bolle Cc: 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, John Crispin Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 986 Lines: 23 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/