From: Mark Brown <broonie@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] ASoC: add es7241 support
Date: Tue, 3 Jul 2018 16:32:12 +0100 [thread overview]
Message-ID: <20180703153212.GC13744@sirena.org.uk> (raw)
In-Reply-To: <20180703132845.26554-1-jbrunet@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
On Tue, Jul 03, 2018 at 03:28:43PM +0200, Jerome Brunet wrote:
> Add support for the es7241 which is a simple 2 channels analog to
> digital converter.
Please don't resubmit patches that have already been applied, you should
submit patches against current code in the tree you're expecting things
to be applied to. If any updates are needed to a patch that's already
been applied you should submit incremental patches which make those
updates. This avoids having to change published git commits which could
cause problems for people working against git.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-03 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 13:28 Jerome Brunet
2018-07-03 13:28 ` [PATCH v3 1/2] ASoC: es7241: add dt-bindings documentation for the es7241 adc Jerome Brunet
2018-07-03 15:34 ` Applied "ASoC: es7241: add dt-bindings documentation for the es7241 adc" to the asoc tree Mark Brown
2018-07-03 13:28 ` [PATCH v3 2/2] ASoC: es7241: add es7241 codec support Jerome Brunet
2018-07-03 15:34 ` Applied "ASoC: es7241: add es7241 codec support" to the asoc tree Mark Brown
2018-07-03 15:32 ` Mark Brown [this message]
2018-07-03 15:36 ` [PATCH v3 0/2] ASoC: add es7241 support Jerome Brunet
2018-07-03 15:41 ` Mark Brown
2018-07-03 15:59 ` Jerome Brunet
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=20180703153212.GC13744@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jbrunet@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®