Return-path: Received: from purkki.adurom.net ([80.68.90.206]:50019 "EHLO purkki.adurom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751795Ab3ANNrN (ORCPT ); Mon, 14 Jan 2013 08:47:13 -0500 From: Kalle Valo To: Eugene Cc: linux-wireless@vger.kernel.org Subject: Re: Custom commands for cfg80211 based driver (like iwpriv) References: <87txqkz0yk.fsf@purkki.adurom.net> <87pq18yqrk.fsf@purkki.adurom.net> <87libwynnt.fsf@purkki.adurom.net> Date: Mon, 14 Jan 2013 15:47:11 +0200 In-Reply-To: (Eugene's message of "Mon, 14 Jan 2013 14:19:43 +0200") Message-ID: <877gnfzxk0.fsf@purkki.adurom.net> (sfid-20130114_144716_472904_72AC7147) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Eugene, Let's keep the discussion in linux-wireless so that everyone can participate. Eugene writes: > Now I got the point. Great! > If the feature will be useful for community I'll post it for sure. > Otherwise I'll use the custom wheel :) I would like to be a bit extreme here. Even if you feel that some feature isn't useful for the community I still recommend sending a small RFC patch and see what kind of feedback you get. It doesn't take much of your time and you never know what's the feedback until you send it, with luck people might be actually interested about your feature! And most of the time people send suggestions how to do it better. Just keep the patches small, don't send any patch bombs and one feature per patch. RFC patches don't need to be perfect as they are just to, as the name implies, Request For Comments :) -- Kalle Valo