From: "Jie, Yang" <yang.jie@intel.com>
To: Mark Brown <broonie@kernel.org>,
Michael Trimarchi <michael@amarulasolutions.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>
Subject: Re: [PATCH] ASoC: Intel: fix a compiling issue
Date: Sun, 19 Apr 2015 01:39:27 +0000 [thread overview]
Message-ID: <E7B1D079BA13FB44A978CC8F69C7D6A905513183@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20150418170304.GW26185@sirena.org.uk>
> -----Original Message-----
> From: Mark Brown [mailto:broonie@kernel.org]
> Sent: Sunday, April 19, 2015 1:03 AM
> To: Michael Trimarchi
> Cc: alsa-devel@alsa-project.org; Jie, Yang; Girdwood, Liam R
> Subject: Re: [alsa-devel] [PATCH] ASoC: Intel: fix a compiling issue
>
> On Sat, Apr 18, 2015 at 02:19:37PM +0200, Michael Trimarchi wrote:
> > On Apr 18, 2015 8:11 PM, "Mark Brown" <broonie@kernel.org> wrote:
>
> > > Rather than have the ifdefs in the users it seems like it'd be
> > > better to fix this by providing static inline stub functions in the
> > > headers. That way nothing else will run into the same trouble.
>
> > This was my "English" suggestion
>
> Yeah, I hadn't seen your mail when I wrote the above.
Thank you, Mark and Michael. Will follow it and send another patch
soon.
~Keyon
prev parent reply other threads:[~2015-04-19 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 2:47 [PATCH] ASoC: Intel: fix a compiling issue Jie Yang
2015-04-13 4:50 ` Michael Trimarchi
2015-04-16 8:17 ` Keyon
2015-04-18 12:11 ` Mark Brown
2015-04-18 12:19 ` Michael Trimarchi
2015-04-18 17:03 ` Mark Brown
2015-04-19 1:39 ` Jie, Yang [this message]
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=E7B1D079BA13FB44A978CC8F69C7D6A905513183@SHSMSX101.ccr.corp.intel.com \
--to=yang.jie@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=michael@amarulasolutions.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.