All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Tc, Jenny" <jenny.tc@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"N, Harshapriya" <harshapriya.n@intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	"Chiang, Mac" <mac.chiang@intel.com>,
	"Nujella, Sathyanarayana" <sathyanarayana.nujella@intel.com>,
	"M R, Sathya Prakash" <sathya.prakash.m.r@intel.com>,
	"M, Naveen" <naveen.m@intel.com>
Subject: Re: [PATCH] ASoC: Intel: Boards: Add Maxim98373 support
Date: Mon, 25 Feb 2019 16:40:38 +0000	[thread overview]
Message-ID: <20190225164038.GA13898@sirena.org.uk> (raw)
In-Reply-To: <20ADAB092842284E95860F279283C56456978C48@BGSMSX104.gar.corp.intel.com>


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

On Mon, Feb 25, 2019 at 04:08:31PM +0000, Tc, Jenny wrote:
> Adding Mark Brown
> 
> A gentle ping for review

As documented in SubmittingPatches please send patches to the 
maintainers for the code you would like to change.  The normal kernel
workflow is that people apply patches from their inboxes, if they aren't
copied they are likely to not see the patch at all and it is much more
difficult to apply patches.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

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



  reply	other threads:[~2019-02-25 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  4:24 [PATCH v2] ASoC: Intel: Boards: Add Maxim98373 support Jenny TC
2019-02-19  4:24 ` [PATCH] " Jenny TC
2019-02-25 16:08   ` Tc, Jenny
2019-02-25 16:40     ` Mark Brown [this message]
2019-02-25 16:47 [PATCH v2] " Jenny TC
2019-02-25 16:47 ` [PATCH] " Jenny TC
2019-03-05 11:06   ` Chiang, Mac
2019-03-07  1:08     ` Tc, Jenny
2019-03-07  9:56       ` Mark Brown

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=20190225164038.GA13898@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=harshapriya.n@intel.com \
    --cc=jenny.tc@intel.com \
    --cc=mac.chiang@intel.com \
    --cc=naveen.m@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sathya.prakash.m.r@intel.com \
    --cc=sathyanarayana.nujella@intel.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.