From: Mike Rapoport <mike-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
To: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Mark Brown
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
Cc: "alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org"
<alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2] ASoC: tegra: TrimSlice machine support
Date: Tue, 26 Apr 2011 11:14:00 +0300 [thread overview]
Message-ID: <4DB67EC8.60601@compulab.co.il> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF04973BB84D-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
On 04/21/11 20:01, Stephen Warren wrote:
> Mike Rapoport wrote at Thursday, April 21, 2011 4:27 AM:
[ snip ]
>> + tristate "SoC Audio support for TrimSlice board"
>> + depends on SND_SOC_TEGRA && MACH_TRIMSLICE && I2C
>> + default m
>
> Mark just removed all the "default" lines from Kconfig, to allow Kconfig
> to determine default policy.
I don't see the 'default' lines being removed from Kconfig in the Mark's tree.
Mark, would you prefer me to drop the 'default' or keep it for consistency with
other entries?
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2011-04-26 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 10:26 [PATCH v2] ASoC: tegra: TrimSlice machine support Mike Rapoport
[not found] ` <1303381618-19730-1-git-send-email-mike-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2011-04-21 17:01 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF04973BB84D-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-04-26 8:14 ` Mike Rapoport [this message]
2011-04-26 8:27 ` 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=4DB67EC8.60601@compulab.co.il \
--to=mike-utxizqzc01rs1mouv/rt9w@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
/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