All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jack Yu <jack.yu@realtek.com>
Cc: "Oder Chiou" <oder_chiou@realtek.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"kent_chen@realtek.com [陳建宏]" <kent_chen@realtek.com>,
	陳昶志 <kenny_chen@realtek.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"tzungbi@google.com" <tzungbi@google.com>,
	"Derek [方德義]" <derek.fang@realtek.com>,
	"Shuming [范書銘]" <shumingf@realtek.com>,
	"Flove(HsinFu)" <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt1015p: add new acpi id and comapatible id
Date: Mon, 9 Aug 2021 12:38:25 +0100	[thread overview]
Message-ID: <20210809113825.GB4866@sirena.org.uk> (raw)
In-Reply-To: <423b6c6b835e431da2f196036ac2ab4f@realtek.com>

[-- Attachment #1: Type: text/plain, Size: 703 bytes --]

On Mon, Aug 09, 2021 at 08:52:49AM +0000, Jack Yu wrote:
> Hi Mark,
> 
> Could you help to review below patch? 
> https://patchwork.kernel.org/project/alsa-devel/patch/20210317062309.14051-1-jack.yu@realtek.com/
> I'm not sure if you miss this patch or not.

Please don't send content free pings.  Sending content free pings adds
to the mail volume (if they are seen at all) which is often the problem
and since they can't be reviewed directly if something has gone wrong
you'll have to resend the patches anyway, so sending again is generally
a better approach though there are some other maintainers who like them
- if in doubt look at how patches for the subsystem are normally handled.

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

  parent reply	other threads:[~2021-08-09 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  6:23 [PATCH] ASoC: rt1015p: add new acpi id and comapatible id Jack Yu
     [not found] ` <423b6c6b835e431da2f196036ac2ab4f@realtek.com>
2021-08-09  9:59   ` Tzung-Bi Shih
2021-08-09 11:38   ` Mark Brown [this message]
2021-08-09 15:54 ` 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=20210809113825.GB4866@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=derek.fang@realtek.com \
    --cc=flove@realtek.com \
    --cc=jack.yu@realtek.com \
    --cc=kenny_chen@realtek.com \
    --cc=kent_chen@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=shumingf@realtek.com \
    --cc=tzungbi@google.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.