From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
"Liao, Bard" <bard.liao@intel.com>
Subject: Re: [PATCH] soundwire: intel: trap TRIGGER_SUSPEND in .trigger callback
Date: Mon, 9 Aug 2021 15:52:30 +0100 [thread overview]
Message-ID: <20210809145230.GD4866@sirena.org.uk> (raw)
In-Reply-To: <acef4e19-dd85-a079-341b-4b26b45c8efb@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
On Mon, Aug 09, 2021 at 09:26:51AM -0500, Pierre-Louis Bossart wrote:
> >>> For Intel machine drivers, all BE dailinks use
> >>> .no_pcm = 1 (explicit setting)
> >>> .nonatomic = 0 (implicit).
> >>
> >> that was my question, how is it implicit?
> >> Should be explicitly set, right?
> implicit behavior with C, if you don't set a field its value is zero...
Only for things declared static.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-09 14:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 5:32 [PATCH] soundwire: intel: trap TRIGGER_SUSPEND in .trigger callback Bard Liao
2021-07-27 6:30 ` Takashi Iwai
2021-07-27 14:12 ` Pierre-Louis Bossart
2021-08-02 4:35 ` Vinod Koul
2021-08-02 5:49 ` Takashi Iwai
2021-08-02 6:29 ` Vinod Koul
2021-08-02 7:29 ` Liao, Bard
2021-08-02 15:46 ` Pierre-Louis Bossart
2021-08-06 13:37 ` Vinod Koul
2021-08-06 16:17 ` Pierre-Louis Bossart
2021-08-09 4:02 ` Vinod Koul
2021-08-09 7:24 ` Takashi Iwai
2021-08-09 14:26 ` Pierre-Louis Bossart
2021-08-09 14:52 ` Mark Brown [this message]
2021-08-09 15:12 ` Takashi Iwai
2021-08-09 15:35 ` Pierre-Louis Bossart
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=20210809145230.GD4866@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.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.