Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Shuming [范書銘]" <shumingf@realtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"Flove(HsinFu)" <flove@realtek.com>,
	"Oder Chiou" <oder_chiou@realtek.com>,
	"Jack Yu" <jack.yu@realtek.com>,
	"Derek [方德義]" <derek.fang@realtek.com>
Subject: RE: [PATCH 1/3] soundwire: intel_auxdevice: add rt766/rt767 codec to wake_capable_list
Date: Thu, 24 Sep 2026 05:18:15 +0000	[thread overview]
Message-ID: <7a61abc07cd2469289d877b70723b973@realtek.com> (raw)
In-Reply-To: <arPHDk4C5U4xAonI@sirena.co.uk>

> >
> > rt766/rt767 have wake capability. Add it to the wake_capable_list.
> 
> As I think I've mentioned before your patch serieses are always posted a bit
> strangely, they're not threaded together and you never supply a cover letter.
> This makes it hard to work with them, tooling gets confused by the
> non-standard presentation.
> 
> You might want to look at b4 to send the patches, especially it's web
> submission endpoint which avoids having to configure mail:
> 
>    https://b4.docs.kernel.org/en/latest/contributor/overview.html

Sorry, will use b4 tool to send v2 and supply a cover letter.


  reply	other threads:[~2026-09-24  5:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 11:01 [PATCH 1/3] soundwire: intel_auxdevice: add rt766/rt767 codec to wake_capable_list shumingf
2026-09-23 12:33 ` Mark Brown
2026-09-24  5:18   ` Shuming [范書銘] [this message]
2026-09-24 17:13     ` 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=7a61abc07cd2469289d877b70723b973@realtek.com \
    --to=shumingf@realtek.com \
    --cc=broonie@kernel.org \
    --cc=derek.fang@realtek.com \
    --cc=flove@realtek.com \
    --cc=jack.yu@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=oder_chiou@realtek.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