All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jonathan Bennett <jbscience87@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Nicolin Chen <nicoleotsuka@gmail.com>,
	Aaron Kling <webgeek1234@gmail.com>,
	Igor Grinberg <grinberg@compulab.co.il>,
	Valentin Raevsky <valentin@compulab.co.il>,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: Request for comments for SND_SOC_IMX_WM8731
Date: Fri, 24 Oct 2014 17:19:02 +0100	[thread overview]
Message-ID: <20141024161902.GI3729@sirena.org.uk> (raw)
In-Reply-To: <CAB-pspe+NP-bvBF=wm-3EQjMw7mvzSeAEH1O-j_fen=L50mkNw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 371 bytes --]

On Fri, Oct 24, 2014 at 09:48:37AM -0500, Jonathan Bennett wrote:

> Oh, also, this patch is a bit big for the mailing list, what is the
> preferred method for sending in large patches to look at? I can attach,
> throw it on github, put it on an http server, etc.

You need to follow the procedure in SubmittingPatches, that means you
need to post your code to the list.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2014-10-24 16:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  4:42 Request for comments for SND_SOC_IMX_WM8731 Jonathan Bennett
2014-10-24 12:20 ` Fabio Estevam
2014-10-24 14:04   ` Mark Brown
2014-10-24 14:10     ` Fabio Estevam
2014-10-24 14:48       ` Jonathan Bennett
2014-10-24 14:56         ` Fabio Estevam
2014-10-24 15:09           ` Fabio Estevam
2014-10-24 16:19         ` Mark Brown [this message]
2014-10-24 16:33           ` Jonathan Bennett
2014-10-24 16:36             ` Mark Brown
2014-10-26  7:40   ` Nicolin Chen

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=20141024161902.GI3729@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=festevam@gmail.com \
    --cc=grinberg@compulab.co.il \
    --cc=jbscience87@gmail.com \
    --cc=nicoleotsuka@gmail.com \
    --cc=valentin@compulab.co.il \
    --cc=webgeek1234@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.