Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: John Crispin <john@phrozen.org>
To: linux-mips@linux-mips.org, ryazanov.s.a@gmail.com
Subject: Re: Introducing Atheros AR231x/AR531x WiSoC support
Date: Wed, 18 Jun 2014 13:49:41 +0200	[thread overview]
Message-ID: <53A17CD5.2060504@phrozen.org> (raw)
In-Reply-To: <CAHNKnsSMvc+VeKumoDY5doR4YDhZ+3ezgY903uHnFH7BGQ+XRQ@mail.gmail.com>



On 18/06/2014 13:46, Sergey Ryazanov wrote:
> 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?
> 

Hi Sergey,

is the code already in a cleaned up state ? are you just missing the
bit where you split it up into patches or is there still dev work that
needs to be done beyond the actual submission process ?

is your code already available somewhere or do you plan to pusht he
owrt support upstream as is ?

	John

  reply	other threads:[~2014-06-18 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 11:46 Introducing Atheros AR231x/AR531x WiSoC support Sergey Ryazanov
2014-06-18 11:49 ` John Crispin [this message]
2014-06-18 12:51   ` Sergey Ryazanov
2014-06-18 13:02     ` John Crispin
2014-06-18 13:12       ` Sergey Ryazanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53A17CD5.2060504@phrozen.org \
    --to=john@phrozen.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ryazanov.s.a@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox