linux-mips
[Top] [All Lists]

Introducing Atheros AR231x/AR531x WiSoC support

To: Linux MIPS <linux-mips@linux-mips.org>
Subject: Introducing Atheros AR231x/AR531x WiSoC support
From: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Date: Wed, 18 Jun 2014 15:46:01 +0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=3GiUb1ND1eJymUp9NUiL2nMieoiwZ4Hb5rJAkGxBZKE=; b=s/qbqBM+UQlviFS+jnr+rWW68aGxRvJPeBxVn52TJ5+4S1Fpb4pPUQcHKJ/BAPTgcI wGcEVwDQb4/Y9seeJykzRE0ujatVhFjidLpBAnghT/1rqnxC+PwqufX/SFBOI6bf6RYa FaYUX6PUtacZCbJNvdHVdiIQDP+pqUWcGivJ4fPQyR7Bs/+/EmMK779Ns2n6Idvb9mQ0 VICqCdTdnw13sroDzldIyHD9uED5eCpoAeGpi1AEGXQ+ZQOYdcjMPdDO8dlGqJsGtplf /6/siXgxt3rW3QUL0DLsJ7W6Fu78wr7qJCIN8lofEBhkE4FMbrLwDGlhnTQw6+HWdRbC IHuQ==
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-id: linux-mips <linux-mips.eddie.linux-mips.org>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
Hello,

I plan to send several patches for upstream merging, that introduce
support for Atheros AR231x/AR531x WiSoCs. This code developed and
extensively tested in OpenWRT project. And I need some help.

I need to know what is the preferred way to split code on to separate
patches suitable for review and merging? Some kind of howto or article
would be great. Could you recomend something? Should I send a series
as RFC first?

-- 
BR,
Sergey

<Prev in Thread] Current Thread [Next in Thread>